Status
datadata is a working prototype. It runs real applications (the apps in its own monorepo are built on it), but it is being actively reshaped and backwards compatibility is explicitly not a goal yet.
Maturity at a glance
Section titled “Maturity at a glance”| Area | State |
|---|---|
| Core client/server sync, optimistic updates | Solid, exercised daily |
| JSON Patch changes with guarded writes | Solid, with known RFC issues |
| Yjs rich-text integration | Solid |
| Session client (staging, conflict preview, commit) | Newer, converging fast |
| Schemas as documents, migrations | Working; dynamic runtime schemas are experimental |
| Cloudflare Durable Object backend | Production shape for our apps |
| Projection layer (per-document views) | Reads work over the full synced document; writable lenses very alpha |
| Offline support, permissions, log compaction, presence | Missing — see Limitations |
Not open source (yet)
Section titled “Not open source (yet)”The source isn’t public yet — partly because the API is still moving, and partly because honest docs felt like the right first artifact. This site documents how datadata works and why, so that:
- application developers can evaluate the model before betting on it, and
- sync-engine developers can compare notes on the design.
If you want to look closer, try it, or argue with a design decision, get in touch.
How gaps are documented
Section titled “How gaps are documented”Every page on this site flags its own gaps inline, and the Known issues & open questions section aggregates them with full write-ups. If something reads as more finished than it is, that’s a bug in the docs — tell us.