BUILD · NO-CODE DATA
From data model to live application — before lunch.
Model your entities, adopt the database you already run, and publish a working screen with no code. Every screen is tenant-isolated and role-gated the moment it ships.
ENTITY DESIGNER
Design the model. Draw the relations.
Twenty-one field types — text, number, date, select, attachment, and computed Formula and Rollup that preview live as you type.
Relate entities on a drag-to-relate ERD canvas: many-to-one and many-to-many, each with an on-delete policy. It compiles to real Postgres tables — or instant virtual storage when you want no schema change.
- 1 Point at schema
- 2 Conformance report
- 3 Choose tenancy
- 4 Adopt — non-destructive
ADOPT YOUR DATABASE
Point it at the Postgres you already run.
The adopt wizard reads a real schema, produces a conformance report, and never alters your data destructively. You choose the tenancy model before anything is written.
What conforms is adopted as-is; what is missing is listed, not forced. You decide.
PUBLISH
Publish, and it is a working screen.
One publish gives you a sidebar entry and a full CRUD grid. Switch the same data between seven view formats — no rebuild, no redeploy.
Publishing is role-gated, and a breaking-change diff shows exactly what a schema change would alter before it goes live.
7 view formats. Zero code.
FORMS
Forms that ship exactly what you see.
The form editor paints on the real runtime form — what you arrange is what your users get. No separate preview to drift out of sync.
Multi-step flows and dependent fields are drag-and-drop, over twenty field components.
ISOLATED BY CONSTRUCTION
Every screen is tenant-isolated and role-gated — by construction.
Isolation is not a setting you remember to switch on. Any model with a tenant column is filtered at the database layer through row-level security, and every publish is scoped to the roles you name. Safe is the default state, not the careful one.
Row-level security
Tenant data is filtered in the database, not the app — a query cannot reach across tenants.
Enforced at the row.
Role-gated publish
Every screen and action is scoped to the roles you assign. Visibility follows the role, not the URL.
Default deny.
Breaking-change diff
Before a schema change ships, a diff spells out exactly what it alters.
See it before it lands.
Model it, publish it, and it is already governed.
The screen your team builds is the same governed surface an agent operates. Start with the data.