GIZ CORE / MODEL RUNTIME
Data, screens, permissions and actions defined in one model.
Giz Core defines data structure, screens, permissions and business actions in one declarative model that screens, APIs and agents all use.
Architecture illustration
When one new field means changing every layer
Most business systems keep the database, server API, screens and validation rules separately. Adding one field means changing several places and redeploying, and the layers drift apart along the way.
Giz Core declares data structure, screens, role permissions and business actions in one model. Screens, REST and OData APIs and agent tools all read the same model.
Key characteristics
| Characteristic | What it means |
|---|---|
| One model | Fields, relations, layout, permissions and validation are defined in one place |
| Model changes while running | Model changes are reloaded on a running server; structural data changes go through a migration review |
| Request-scoped transactions | Changes within a request are saved together or rolled back together |
| Standard building blocks | Grids, forms, charts, kanban boards and Gantt charts compose business screens |
| Standard APIs | REST and OData expose the same data and permissions |
What changes in an implementation
New work is built by adding models, screens and rules. Permissions, change history and APIs come with the model. Timelines depend on scope and integrations, so the scope is agreed after checking a representative workflow first.
Giz Core is the fourth-generation engine of the Occam platform first developed at Exinno.
Business applications · Platform architecture · Company history
YOUR NEXT STEP
Bring us the workflow that needs to work.
Start with the files and systems you use today, and the work you want to change.