Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
LiveStore
Event-sourced client state framework where an event log syncs via pluggable backends and is materialized into reactive SQLite on each client.
livestore.devActive
v0.5.0 released 2026-10-15 (pre-1.0) (checked 2026-10-25)
In Local-first
Where it stands apart
- Which shared standard or format does it mainly build on? SQLite on the client (14% of 21 others)
- What shape of data does your app read and write? an event log (0% of 19 others)
- Where does it keep data on the client by default, on its main platform? SQLite (19% of 21 others)
What it shares with most of the community
- Is it actively maintained? active (76% of 21 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (67% of 21 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (81% of 21 others)
- Do you need an account to use it? no account (71% of 21 others)
- Who is it for? developers (90% 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)
- What does it need to sync between devices? (first that applies) a sync server or relay (yours or hosted) (52% of 21 others)
- If the company behind it disappeared, would apps keep working? yes (81% of 21 others)
- Is end-to-end encryption built in? no (80% of 20 others)
Nearest neighbors
- TinyBase 76% of 17 shared answers match
- Evolu 72% of 18 shared answers match
- Automerge 61% of 18 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active v0.5.0 released 2026-10-15 (pre-1.0) | 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) v4: from the map's own 'license' question. Apache-2.0 | source 2026-10-25 |
| How is it mainly sustained? | community, foundation, or research v4: from the map's own 'business' question. Sponsorship-funded by creator Johannes Schickling. | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes v4: from the map's own 'self_host' question. | source 2026-10-25 |
| Do you need an account to use it? | no account Open-source client framework with pluggable backends; no maker account mentioned. | source 2026-10-26 |
| Who is it for? | developers v4: from the map's own 'audience' question. | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart SQLite on the client Event log materialized into SQLite on each client. | 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 | source 2026-10-25 |
| What does it need to sync between devices? (first that applies) | a sync server or relay (yours or hosted) Needed for multi-device sync (Cloudflare, ElectricSQL, S2 or custom provider); works local-only without one. | source 2026-10-25 |
| If the company behind it disappeared, would apps keep working? | yes Open source, community project; sync backends are self-run. | source 2026-10-25 |
| Is end-to-end encryption built in? | no Encryption is documented as an app-level pattern, not built in. | source 2026-10-25 |
| What shape of data does your app read and write? | stands apart an event log Events materialized into SQLite state. | source 2026-10-25 |
| How are concurrent edits resolved? (first that applies) | a server decides (it rebases or rejects client writes) Sync backend imposes a total order; clients rebase pending events on upstream. Merge-conflict detection 'isn't implemented yet'. | source 2026-10-25 |
| Where does synced data live on the server side? | in its own sync server or relay Event log stored by the sync provider (e.g. Durable Objects, S2, Postgres via Electric). | source 2026-10-25 |
| Where does it keep data on the client by default, on its main platform? | stands apart SQLite SQLite (WASM + OPFS on web, native on Expo). | source 2026-10-25 |
| How much data syncs to each client? | whichever documents or stores the app opens Whole event log per store (storeId); no partial sync within a store. | source 2026-10-25 |
| Which platforms are first-class? | JavaScript on web and mobile (React Native, Expo, Capacitor) Web, Expo, Node, Electron, Tauri, Cloudflare DO. | source 2026-10-25 |
| Are auth and permissions built in? | no, bring your own Auth is a pattern (sync payload checked by your backend). | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/livestorejs/livestore · read 2026-10-25
- Web page · docs.livestore.dev/ · read 2026-10-25
- Web page · docs.livestore.dev/building-with-livestore/syncing/ · read 2026-10-25
- Web page · docs.livestore.dev/patterns/auth/ · read 2026-10-25
- Web page · docs.livestore.dev/patterns/encryption/ · read 2026-10-25
- Web page · docs.livestore.dev/patterns/offline/ · read 2026-10-25
- Web page · docs.livestore.dev/platform-adapters/web-adapter/ · read 2026-10-25
- Web page · docs.livestore.dev/sustainable-open-source/sponsoring/ · read 2026-10-25
- Web page · docs.livestore.dev/sync-providers/custom/ · read 2026-10-25
- Web page · livestore.dev · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.