Skip to content

FOUNDATIONS · DATA MODEL

A typed graph.
Not a pile of tables.

Objects, events and views — connected by typed edges you can query, navigate and reason about. Click a node to inspect its shape.

  • KINDSOBJECT · EVENT · VIEW
  • EDGEShasMany · refs · emits
  • EVOLUTIONschema-on-write
  • QUERYtyped + NL

DATA MODEL · GRAPH INSPECTOR

Click a node. Read the shape.

Your tenant is a typed graph — objects, events and views — not a pile of tables. Pick a node to inspect its schema, follow the edges to see what it references and what it emits.

hasManyrefsrefsemitsrefsrefsOBJECTAccountOBJECTDealOBJECTUserEVENTEventVIEWRevenueView
OBJECT

Deal

A revenue opportunity tied to an account.

  • iduuid
  • account_idref→ Account
  • stageenumnew|qualified|won|lost
  • amountnumber
  • close_datedatetime
  • owner_idref→ User

HOW THE GRAPH EVOLVES

Schema grows with writes.

A write declares fields it needs. The runtime resolves against the current schema, updates it if safe, and emits a schema-change event — everything downstream sees the new shape.

WRITE

Write request

typed payload

CHECK

Schema check

compat diff

APPLY

Apply + emit

event.schema.*

VIEW

Views refresh

materialised

NOTIFY

Clients notify

push · CRDT

PLATFORM · CLOSE THE LOOP

A graph that fits your business, not the other way around.

Your objects, your edges, your vocabulary. The schema evolves with writes — and every change leaves a typed event behind.