PostgreSQL read-path synchronization

Electric

An open-source read-path sync engine that streams PostgreSQL subsets called Shapes to local clients and services over HTTP.

Editorial verdict

Choose Electric when PostgreSQL Shapes, HTTP delivery, and application-owned writes form a clean architecture; do not choose it under the assumption that current Electric provides bidirectional offline synchronization.789

Best for

  • PostgreSQL applications that need reactive subsets delivered over HTTP
  • Teams keeping business logic, authorization, and writes in an existing API
  • Architectures that benefit from CDN-compatible fan-out and local client stores
789

Not ideal for

  • Products requiring the sync engine itself to support offline writes
  • Teams expecting the retired legacy bidirectional ElectricSQL architecture
  • Applications unable to operate PostgreSQL logical replication, Shape authorization, and a separate write path
789
Main trade-off

Electric gives a composable PostgreSQL read path and leaves writes flexible, but the application must own write UX, mutation APIs, authorization, optimistic reconciliation, and offline limitations.789

Product boundary

Whether reactive PostgreSQL read-path synchronization is enough when writes remain explicitly owned by the application.

Current Electric Sync is a read-path engine. It streams Shapes out of PostgreSQL but does not provide a built-in write-path sync or the legacy ElectricSQL bidirectional product model.7810

For: PostgreSQL teams that need live application-specific data subsets without adopting a sync engine that owns the write path

  • The product requires the sync engine to accept writes during prolonged offline periods.
  • Shape authorization or data selection cannot safely express tenant and revocation boundaries.
  • The team cannot own the application write API, optimistic state, rejection, and reconciliation behavior.
  • Cloud write and retention economics or self-hosted replication operations do not fit.

Why teams consider Electric

  • Shape-based read pathShapes define PostgreSQL subsets that are streamed over HTTP to subscribed clients and services.7
  • Composable writesApplications keep their existing API and can choose online, optimistic, persistent optimistic, or custom write patterns.8
  • Open deploymentElectric Sync is Apache-2.0 open-source software with self-hosting and Electric Cloud routes.710

Pricing

Electric Sync is open-source software with no separate software license fee when self-hosted; infrastructure and operations remain the team's cost. Electric Cloud charges for writes and retention, with additional service cost for Postgres Sync, while reads, egress, fan-out, concurrent users, and delivery are listed as free.9

Read-path estimate

Self-hosted, PAYG, Pro, Scale, or Enterprise

Model filtered Shape-log writes, retention, Postgres Sync service charges, plan minimums or credits, database count, support, and self-hosted infrastructure.9

Cloud base meters
Writes and retained data, plus the current Postgres Sync service surcharge9
Listed free dimensions
Reads, egress, fan-out, concurrent users, and data delivery9
Self-host boundary
Apache-2.0 software plus PostgreSQL, infrastructure, availability, and operations9
Pricing checked View official pricing

Electric vs alternatives

PowerSync

Choose when
Choose PowerSync when client-local SQLite and offline-capable writes are primary requirements.
Compared with Electric
PowerSync introduces a fuller synchronization service, write-flow, conflict, and usage model.15

Zero

Choose when
Choose Zero when query-driven TypeScript web synchronization and optimistic online mutations fit better than Shape delivery.
Compared with Electric
Zero has a larger application framework and server topology and does not support offline writes.161718

Replicache

Choose when
Use it only as the installed system being maintained or migrated.
Compared with Electric
It is not a current new-project route because it is in maintenance mode.1112

Resources and sources

Official product, architecture, status, and pricing

  • Electric Sync documentation
    Open
  • Electric write-path guide
    Open
  • Electric Cloud pricing
    Open
  • Electric Sync open-source product page
    Open
  1. 1
    PowerSync philosophy and architecture

    PowerSync · Accessed Official

  2. 2
    PowerSync Sync Streams and Sync Rules

    PowerSync · Accessed Official

  3. 3
    PowerSync self-hosting

    PowerSync · Accessed Official

  4. 4
    PowerSync feature status

    PowerSync · Accessed Official

  5. 5
    PowerSync pricing

    PowerSync · Accessed Official

  6. 6
    PowerSync source and licensing overview

    PowerSync · Accessed Official

  7. 7
    Electric Sync documentation

    Electric · Accessed Official

  8. 8
    Electric write-path guide

    Electric · Accessed Official

  9. 9
    Electric Cloud pricing

    Electric · Accessed Official

  10. 10
    Electric Sync open-source product page

    Electric · Accessed Official

  11. 11
    Replicache product and maintenance status

    Rocicorp · Accessed Official

  12. 12
    Archived Replicache source repository

    Rocicorp · Accessed Official

  13. 13
    Zero introduction

    Rocicorp · Accessed Official

  14. 14
    Zero project status

    Rocicorp · Accessed Official

  15. 15
    When to use Zero

    Rocicorp · Accessed Official

  16. 16
    Zero mutators

    Rocicorp · Accessed Official

  17. 17
    Zero connection and offline behavior

    Rocicorp · Accessed Official

  18. 18
    Self-hosting Zero

    Rocicorp · Accessed Official

  19. 19
    Zero open-source policy

    Rocicorp · Accessed Official

  20. 20
    Zero product and managed-service pricing

    Rocicorp · Accessed Official