Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
DXOS
Decentralized app framework (ECHO Automerge-based DB, HALO identity, MESH P2P networking) whose main product is now the Composer collaborative workspace; relicensed to FSL.
dxos.orgActive
v0.14.0 tagged 2026-10-10; daily commits (mostly Composer); docs.dxos.org did not resolve when checked (checked 2026-10-25)
In Local-first
Where it stands apart
- How is the main thing licensed? copyleft or source-available with restrictions (19% of 21 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? partly (some features need the maker's servers) (14% of 21 others)
- Who is it for? both (0% of 21 others)
- Which shared standard or format does it mainly build on? Automerge (5% of 21 others)
- If the company behind it disappeared, would apps keep working? partly, data survives but sync would break (10% of 21 others)
- Which platforms are first-class? JavaScript on web and server only (19% of 21 others)
What it shares with most of the community
- Is it actively maintained? active (76% of 21 others)
- How is it mainly sustained? company with a paid product, tier, or ads (62% of 21 others)
- Do you need an account to use it? no account (71% of 21 others)
- Does an app built on it keep working fully offline, for both reads and writes? yes, full offline reads and writes (86% of 21 others)
Not documented
The public sources we read don't say:
- Is end-to-end encryption built in?
Nearest neighbors
- Anytype (any-sync) 59% of 17 shared answers match
- Ditto 53% of 17 shared answers match
- Dexie Cloud 50% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active v0.14.0 tagged 2026-10-10; daily commits (mostly Composer); docs.dxos.org did not resolve when checked | 2026-10-25 |
| How is the main thing licensed? | stands apart copyleft or source-available with restrictions v4: from the map's own 'license' question. FSL-1.1-Apache-2.0 (converts to Apache after 2 years); homepage still says 'fully open source' | source 2026-10-25 |
| How is it mainly sustained? | company with a paid product, tier, or ads v4: from the map's own 'business' question. Company; Composer plus hosted EDGE services (low confidence on monetization) | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | stands apart partly (some features need the maker's servers) v4: from the map's own 'self_host' question. Code is available but EDGE/signaling infra is DXOS-run by default; self-hosting not documented | source 2026-10-25 |
| Do you need an account to use it? | no account Homepage says user identity is handled natively by the client API (decentralized), no maker account. | source 2026-10-26 |
| Who is it for? | stands apart both v4: from the map's own 'audience' question. SDK for devs and the Composer app for end users | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart Automerge ECHO database is built on Automerge. | source 2026-10-26 |
| Does an app built on it keep working fully offline, for both reads and writes? | yes, full offline reads and writes Client-first local database | source 2026-10-25 |
| What does it need to sync between devices? (first that applies) | nothing extra: devices can sync peer-to-peer or over any transport Site says the only server needed serves the app shell; P2P over WebRTC still needs signaling, and recent releases add DXOS EDGE services | source 2026-10-25 |
| If the company behind it disappeared, would apps keep working? | stands apart partly, data survives but sync would break Local data persists; relies on DXOS-run signaling/EDGE for sync | source 2026-10-25 |
| Is end-to-end encryption built in? | Not documented HALO key-based identity; no explicit E2EE claim found on current pages | source 2026-10-25 |
| What shape of data does your app read and write? | JSON-like documents ECHO objects backed by Automerge | source 2026-10-25 |
| How are concurrent edits resolved? (first that applies) | merged automatically, keeping both edits where possible (CRDT text, lists, maps) | source 2026-10-25 |
| Where does synced data live on the server side? | nowhere it manages (peers, or plain files and object storage) | source 2026-10-25 |
| Where does it keep data on the client by default, on its main platform? | IndexedDB or other browser storage Browser storage (OPFS/IndexedDB) | source 2026-10-25 |
| How much data syncs to each client? | everything the user can access Syncs the spaces the identity is a member of | source 2026-10-25 |
| Which platforms are first-class? | stands apart JavaScript on web and server only | source 2026-10-25 |
| Are auth and permissions built in? | yes HALO identity and space membership | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/dxos/dxos · read 2026-10-25
- Web page · dxos.org · read 2026-10-25
- Web page · dxos.org/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.