Join the waitlist to take part in the alpha.
Engineering ·

The schema as the single source of truth

UI, API, validation, permissions: everything derives from one definition. What that changes for teams building on Standards.

In most business software, the same information is described four times: in the database, in the API, in the forms, in the access rules. Four descriptions, four chances to drift apart.

Standards takes the opposite stance: the schema is written once, by a developer, and everything else derives from it: views, validation, permissions, down to the TypeScript types on the client.

Developer-defined, team-extended

The schema is not frozen. Protected system attributes guarantee the foundation holds; teams add their own fields at runtime, Notion-style, but with the type inference of a real framework.

That double layer is what lets a private wealth firm model qualified relationships (“I own this company”, “I hold usufruct on this property”) without waiting for a release.