A connected model.
A history you can inspect.
Connect your application’s records, relationships, and source history. Explore the model in a workspace you can build, query, and change.
Not everything is a pair of records.
A subscription connects a customer, a product, and a plan. Give each participant a named role in one relationship atom, then define which routes a query can follow.
Define types in Schema, then create atoms of those types in Data. The demo validates each write against the accepted catalog.
Open SchemaKeep the inputs behind the records.
Import JSON or CSV and retain the input snapshot. Inspect a record’s latest source, then use its history to find earlier values and observations.
The sample connects a customer directory, application catalog, subscription ledger, and service observations. Your own model can describe something entirely different.
Import and inspect sourcesGo beyond what matches.
See why it belongs.
Filter records and follow typed relationships in either direction. Inspect the paths, named participants, and sources associated with the result.
In the demo’s enterprise-exposure query, the plan and affected product must belong to the same subscription. A connection is useful only when its meaning is preserved.
Run the connected query| Account | Degraded dependencies |
|---|---|
| Aster Labs | Payments, Reporting |
| Copperline | Payments |
| Fieldwork | Reporting |
Change the record.
Keep the earlier view.
A recovery observation updates the Payments service and its incident together. The enterprise-exposure query now finds two accounts instead of three.
Select the earlier revision to recover the previous answer. Restoring an individual record creates a new revision; it does not rewind unrelated records.
Explore the revision historyStart empty.
Leave with your work.
Define types for your own application, import non-sensitive data, save queries locally, and export results. Download the complete workspace to retain its records, schema, sources, and revision history.
Application views illustrate filtered access to the same dataset. They are read-only previews, not production identity or security boundaries.
Create an empty workspaceThe best explanation
is a working workspace.
The demo implements the model, queries, and edits described here using a local reference engine. Hosted service availability, API contracts, and production guarantees are separate.
Read the demo’s scope