DXOS

P2P Platform

A local-first application platform whose three co-designed components are exposed to developers through a single SDK: ECHO, a peer-to-peer graph database built on the Automerge CRDT that gives every app transparent replication and automatic conflict resolution; HALO, a public/private-key identity and contact system that authenticates users and devices without a server; and MESH, a peer-to-peer networking layer that forms a mesh between peers, minimising connections while preserving connectivity and redundancy. Applications built on DXOS run without centralized server infrastructure — data lives on user devices and syncs directly between peers.

Comunidade
Links
Visitar Comunidade

Detalhes

Licença Permissive (MIT) — DXOS packages including the ECHO modules and @dxos/automerge are published under MIT with DXOS copyright from 2022. https://github.com/dxos
Status de Dev 🔬 Beta
Proprietário DXOS — open-source project with an associated company; copyright notices on published packages read 'DXOS' from 2022. Specific corporate structure and leadership not confirmed in the sources reviewed
Órgão de Governança Unknown (open-source project with an associated company; corporate structure and leadership not confirmed in available sources)
País Unknown — no headquarters published in the sources reviewed; the project presents as a distributed open-source effort
Ano de Início 2022
Stack TypeScript throughout — ECHO is a peer-to-peer graph database written in TypeScript; SDKs published for React and TypeScript; Automerge (Rust core with JS bindings) provides the CRDT layer
Financiamento Venture-adjacent — BlueYard Capital has publicly engaged with DXOS on local-first development; no funding round amounts confirmed in the sources reviewed
Última Investigação 1 de jul. de 2026

Domínios de Caso de Uso

Platform Evolution & Sovereignty

P2P Platform Atributos

Origins Local-first / collaborative applications — built to let developers ship real-time collaborative, offline-capable apps without operating backend infrastructure, by making replication, identity and peer networking properties of the platform rather than services each app must implement
Database ECHO — a peer-to-peer graph database (the Eventually Consistent Hierarchical Object store) written in TypeScript, built on the Automerge CRDT, providing transparent replication and automatic conflict resolution with local storage on each peer
Query Language ECHO query API exposed through the SDK, with a reactive state container so application state updates automatically as replicated data changes; no separate declarative query language documented in the sources reviewed
Data Formats Automerge CRDT documents as the underlying representation; ECHO schema definitions (@dxos/echo-schema) for typed objects, with support for decentralized schema evolution and data migration
Collaborative Live Editing Collaborative real-time editing (CRDT-based) — ECHO builds on Automerge, so concurrent multi-user editing merges without manual conflict resolution, both in real time and after offline work
Rich Text Editing Supported via Automerge — Automerge provides rich-text CRDT support; DXOS applications inherit it through ECHO
Mobile Support Partial — TypeScript and React SDKs are usable in mobile web and React contexts; no dedicated native mobile SDK documented in the sources reviewed
Web Support Yes — the primary target is browser-based applications built with the React and TypeScript SDKs
Native Apps Partial — applications can be packaged for desktop, but no first-party native application framework is documented in the sources reviewed
Terms Self-hosting / free — MIT-licensed SDK; applications run peer-to-peer without required backend infrastructure. No fees or hosted tier identified in the sources reviewed
Funds Unknown — no figures disclosed in the sources reviewed
Based On Automerge (CRDT layer underlying ECHO — see the Automerge entry on the DD Pro tab); existing internet protocols extended by MESH for peer-to-peer transport; public/private key cryptography for HALO identity. Notably, DXOS composes external building blocks rather than defining its own wire format, which is what places it here rather than on the Integrated P2P Runtime tab
P2P Architecture Mesh network — MESH forms a peer-to-peer mesh between participating peers, optimised to minimise the number of connections while maintaining connectivity and redundancy, extending existing internet protocols rather than defining a new transport. No centralized server infrastructure required
Development Tools DXOS SDK for React and TypeScript, wrapping ECHO, HALO and MESH behind one developer surface; @dxos/echo-schema for typed object definitions; @dxos/automerge integration package; published documentation site and application templates
Deployment Options Peer-to-peer with no required backend — applications deploy as static web apps and sync directly between peers over MESH; signalling infrastructure may be self-hosted. No mandatory cloud service
Authentication & Identity HALO — decentralized identity and contact management using public/private key pairs, providing user authentication and device authorization without a server, with device invitation flows for adding new devices to an identity and peer invitation flows for sharing spaces
Storage Model Local-first — each peer holds a full local replica in ECHO with transparent replication between peers; data persists on user devices and remains available offline, syncing on reconnection
Interoperability Automerge compatibility at the data layer (documents are Automerge CRDTs, which are portable to other Automerge-based tools); standard web platform APIs; listed in the localfirst.fm Local-First Landscape alongside comparable technologies. No federation or cross-platform protocol bridging documented in the sources reviewed
Social Graph Partial — HALO provides identity and contact management, which gives applications a per-user contact list and device graph, but no public social graph protocol is defined