Canonical

Data Platform

Platform

Everything downstream of the schema is generated

One canonical schema definition generates Postgres persistence, validation, admin UI, REST, JSON:API, GraphQL, OpenAPI 3.2, permissions, events and typed SDKs.

Schema registry

Versioned definitions with draft, publish and deprecate states. Publishing previews the diff, flags destructive changes and compiles migrations.

  • · 60+ field kinds
  • · Components & dynamic zones
  • · Relations with cardinality

Generated persistence

Real, typed Postgres tables with system columns, indexes and join tables — not a document blob pretending to be a schema.

  • · Deterministic DDL
  • · Immutable revisions
  • · Rollback from snapshots

Delivery interfaces

REST, JSON:API 1.0, GraphQL with subscriptions, OpenAPI 3.2, server-sent events, webhooks and MCP servers for AI agents.

  • · One query language
  • · Preview tokens per environment
  • · API tokens with scopes

Governance

Role baseline, grant and restrict permission sets, record conditions and field-level security resolved in a fixed order.

  • · Append-only audit log
  • · Access simulator
  • · Tenant hierarchy with RLS

Editorial workflow

Draft, review, scheduled and published states from a single lifecycle engine, with per-field translations and fallbacks.

  • · Scheduled releases
  • · Field-level i18n
  • · Diffed revision history

Developer experience

Typed SDK generation, schema-as-code in version control and a CLI that pulls, diffs, pushes and migrates definitions.

  • · Generated types
  • · Layout & view API
  • · Form descriptors over REST

From definition to delivery

  1. 01

    Define

    Model fields, validation, relations, layout and permissions in one definition.

  2. 02

    Publish

    Preview the diff, compile migrations, version the definition immutably.

  3. 03

    Author

    Generated lists and forms, review workflow, scheduling and translations.

  4. 04

    Deliver

    REST, JSON:API, GraphQL, events and SDKs regenerated from the same registry.

See it applied

Use cases describe how teams model their domain on the platform; business cases explain where the effort is recovered.

Browse use casesRead the business caseEngineering blog

Read next

Go deeper

The architecture and API documents behind the product tour.