Model Builder
Visual relational modeling — entities, attributes, and references defined by pointing and clicking, with auditing, soft deletion, and permissioning declared on the model itself, not bolted on afterward.
Entities, attributes, references
An application starts as entities — contacts, opportunities, activities — each with typed attributes: text, numeric, timestamp, boolean, attachment, reference. All of it defined by pointing and clicking.
References chain. A contact belongs to an entity; an activity points at its contact; an opportunity carries both. The chain is the structure of your business, stated once — and everything generated from the model reads it.
Validation is a real state that names its problem: an attribute with no type reads "Required field," and the model says so until it's fixed — not a warning color you learn to ignore.
Relations do work here
The relation kind is not documentation — it determines what the generated forms can do. A parent relation gives the child its context. A child relation with tabs generates tabbed sub-records; a child relation with master-detail generates inline detail editing.
See what the forms become →What every entity carries
Entity-level filter
Row-level scoping declared once on the entity, inherited by everything that reads it.
Soft deletion
Deleted rows leave the screens, not the record — recoverable, with the history whole.
Permission
Role-based access to the table and the column, enforced at the API — not just hidden on the screen.
Audit
Every column change written as it happens — in system time and business time.
From model to working system
The model is the source, not documentation — what it declares, the platform generates.
A working wireframe
The Entities world of the builder: open an entity, add an attribute, and follow the model relations panel — clicking a neighbor re-centers the graph and opens that entity's editor.