Skip to main content
An application is a custom UI an admin designs through chat and a viewer uses to do their day-to-day work. Where a dashboard shows numbers, an app acts: it edits rows, kicks off side effects, and writes back to ontology entities. Apps are company-scoped—not tied to a single project. One app can read across several entities and write to others.

​
Who does what

The Action endpoint is deliberately the write surface for viewers: an app is an admin-approved write boundary, not a free-for-all.

​
What an app contains

  • Bindings — which entities the app reads from or writes to, and at what mode (read, write, readwrite).
  • Actions — typed write operations (insert row, patch row, delete row) the app’s UI calls.
  • Generated UI — React/TypeScript bundled at deploy time. You don’t author the JSX; the architect does, from your chat description.
  • Versions — every generation produces a new version; you can revert at any time.

​
Next steps