Documents all the way down
User data, schemas, and even the sync engine’s own read-models are all documents, accessed through one small, referential API. Read the core idea.
Documents all the way down
User data, schemas, and even the sync engine’s own read-models are all documents, accessed through one small, referential API. Read the core idea.
Optimistic by default
Changes apply locally the moment they’re made and are confirmed — or cleanly rejected — by an authoritative server. How sync works.
A staging area for changes
The session client lets humans and AI agents stage edits, preview conflicts three-way, and commit atomically. The session client.
Built with agents in mind
Agents use the same API as everything else — including creating their own document types. datadata and AI agents.
Honest about the gaps
This is a prototype. Known issues — including problems we’ve found with the JSON Patch RFC — live in the open. Known issues & open questions.
For sync-engine developers too
Wire protocol, storage model, and the reasoning behind the design. Design decisions.