Local-first collaboration infrastructure
Mavryx is a CRDT-based sync engine for app developers: offline by default, conflict-free merges, peer-to-peer or relayed sync — with data stored wherever your customer demands. Cloud outages become someone else's incident.
TypeScript · Swift · Kotlin · Rust core · MIT-licensed client
Your customers learned three lessons the hard way: outages, invoices, and data sovereignty audits.
When a cloud region blinks, every “collaborative” app becomes a spinner. Users with the file on their own disk keep working. Yours could too.
Every keystroke round-trips through metered infrastructure. Local-first apps sync diffs peer-to-peer — your COGS curve bends the right way.
Procurement now asks for data residency by contract. “In our cloud” loses deals that “on your servers, synced our way” wins.
You build the app. Mavryx handles merge math, transport, and storage policy.
Documents, lists, counters, and rich text that merge without conflicts — mathematically, not “last write wins and pray.” Audited Rust core.
Peer-to-peer over local network, WebRTC across the internet, or our relay when NAT wins. Devices find the fastest path automatically.
Sync targets are pluggable: our cloud, the customer's S3 bucket, their on-prem server, or nothing but devices. Residency becomes a config value.
Relays see ciphertext only. Key exchange rides the same CRDT layer, so even key rotation merges cleanly across offline devices.
const doc = mavryx.doc(schema) — your app state becomes a synced document with the same API you'd write by hand.
Enable P2P, relay, or both; point storage at us, the customer's bucket, or local-only. Three lines of config, swappable per tenant.
Optimistic updates, retry queues, “document was modified” dialogs — gone. Merges are deterministic on every platform, guaranteed by test vectors.
perceived latency — every write is local first
typical sync-related backend code deleted after migration
TypeScript, Swift, Kotlin, Rust — one merge semantics
“Our field-engineering app gets used in basements and on rooftops with zero bars. We spent two years fighting sync bugs before moving to Mavryx. Now offline isn't a feature we maintain — it's just how the app works. And the on-prem storage option closed two enterprise deals our cloud-only competitors couldn't touch.”
Get the SDK, the starter templates, and a relay sandbox. Free for development, forever.
Sent — SDK access and docs link are in your inbox.