Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
ElectricSQL
Read-path sync engine that streams 'shapes' of Postgres data to clients over HTTP, now part of Databricks/Neon and repositioned toward agents.
electric.ax/Active
Acquired: joined Neon at Databricks (announced 2026-08-11); Electric Cloud is winding down; OSS (Postgres Sync, PGlite, TanStack DB, Durable Streams) stays open source. Repo pushed 2026-10-06; electric-sql.com now redirects to electric.ax ('the agent platform built on sync'). (checked 2026-10-25)
In Local-first
Where it stands apart
- Which shared standard or format does it mainly build on? your Postgres (logical replication) (5% of 21 others)
- Does an app built on it keep working fully offline, for both reads and writes? partly (reads only, or only data that was cached) (10% of 21 others)
- Where does synced data live on the server side? in your existing Postgres or other database (19% of 21 others)
- Where does it keep data on the client by default, on its main platform? no default: you pick a storage adapter (24% 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)
- How is it mainly sustained? company with a paid product, tier, or ads (62% 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)
- 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
- Zero (Rocicorp) 94% of 18 shared answers match
- PowerSync 67% of 18 shared answers match
- Triplit 67% of 18 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active Acquired: joined Neon at Databricks (announced 2026-08-11); Electric Cloud is winding down; OSS (Postgres Sync, PGlite, TanStack DB, Durable Streams) stays open source. Repo pushed 2026-10-06; electric-sql.com now redirects to electric.ax ('the agent platform built on sync'). | 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? | company with a paid product, tier, or ads v4: from the map's own 'business' question. Now inside Databricks (Neon/Lakebase); Electric Cloud itself is winding down. | 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 Apache-2.0 open source you self-host against your Postgres; Cloud sign-up only for hosted option. | 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 your Postgres (logical replication) Streams Postgres via logical replication. | source 2026-10-26 |
| Does an app built on it keep working fully offline, for both reads and writes? | stands apart partly (reads only, or only data that was cached) Read-path sync only; writes go through your own API (TanStack DB adds optimistic local writes; offline write queuing is app-level). | source 2026-10-25 |
| What does it need to sync between devices? (first that applies) | a sync server or relay (yours or hosted) | source 2026-10-25 |
| If the company behind it disappeared, would apps keep working? | yes Real-world test: Electric Cloud is shutting down and users are told to self-host; data stays in your Postgres. | source 2026-10-25 |
| Is end-to-end encryption built in? | no | source 2026-10-25 |
| What shape of data does your app read and write? | relational tables (SQL or a relational query language) | source 2026-10-25 |
| How are concurrent edits resolved? (first that applies) | a server decides (it rebases or rejects client writes) Writes go through your backend API, which is authoritative. | source 2026-10-25 |
| Where does synced data live on the server side? | stands apart in your existing Postgres or other database Postgres via logical replication. | source 2026-10-25 |
| Where does it keep data on the client by default, on its main platform? | stands apart no default: you pick a storage adapter Shape data is held in memory by default (TypeScript client / TanStack DB); can persist into PGlite or other stores. | source 2026-10-25 |
| How much data syncs to each client? | subsets chosen by queries Shapes = table + where clause subsets. | source 2026-10-25 |
| Which platforms are first-class? | JavaScript on web and mobile (React Native, Expo, Capacitor) Official TypeScript and Elixir clients plus Expo starter; any HTTP client can consume the protocol. | source 2026-10-25 |
| Are auth and permissions built in? | partly or via hooks Auth via your API/proxy in front of the shape endpoint. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/electric-sql/electric · read 2026-10-25
- Web page · electric.ax/ · read 2026-10-25
- Web page · electric.ax/blog/2026/08/11/electric-joining-databricks · read 2026-10-25
- Web page · electric.ax/docs · read 2026-10-25
- Web page · electric.ax/docs/sync/guides/auth · read 2026-10-25
- Web page · electric.ax/docs/sync/guides/deployment · read 2026-10-25
- Web page · electric.ax/docs/sync/guides/shapes · read 2026-10-25
- Web page · electric.ax/docs/sync/guides/writes · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.