Query-driven web data synchronization

Zero

An Apache-2.0 TypeScript sync engine for reactive client-side queries and optimistic online mutations backed by PostgreSQL.

Editorial verdict

Retain Zero as a formal new-project candidate: the core product is officially GA, fully supported, open-source, and self-hostable. Treat managed Cloud as gated onboarding rather than fully public availability, and reject Zero when offline writes, native clients, or incompatible PostgreSQL and dataset constraints are hard requirements.141517181920

Best for

  • Interactive TypeScript web applications backed by PostgreSQL
  • Teams that want reactive query-driven local data and optimistic online mutations
  • Organizations prepared to self-host Zero or complete the current managed-service onboarding process
141517181920

Not ideal for

  • Applications requiring writes during long or explicit offline periods
  • Native mobile applications or non-TypeScript client requirements
  • Teams unable to operate Zero's PostgreSQL replication, cache, query, mutate, backup, and recovery topology
141517181920
Main trade-off

Zero offers reactive client-first interaction and query-driven synchronization, but it is PostgreSQL- and TypeScript-oriented, does not support offline writes, and requires a substantial server topology or a not-yet-fully-public managed onboarding route.141517181920

Product boundary

Whether Zero's query-driven PostgreSQL architecture and online-write contract fit an interactive TypeScript web application.

Zero is a client-server system with an authoritative PostgreSQL backend, not a general offline-first database. It supports local reads and optimistic online mutations but rejects writes after the client enters disconnected or error states.13141516171819

For: TypeScript web teams building highly interactive PostgreSQL applications that are online for writes and fit Zero's current data and deployment boundaries

  • The product requires offline writes or prolonged offline operation.
  • The client is not a TypeScript web application or the authoritative backend is not compatible PostgreSQL.
  • The synchronized dataset, query model, permissions, schema, or current recommended scale does not fit.
  • The team cannot operate self-hosted topology and managed Cloud onboarding is unavailable or unacceptable.
  • Mutation rejection, rollback, authorization, logical replication, backup, and recovery behavior fail production testing.

Why teams consider Zero

  • Query-driven synchronizationClient queries determine the data synchronized into Zero's normalized local datastore.13151618
  • Optimistic online mutationsMutators run locally first, then execute through an application-owned server endpoint and reconcile from PostgreSQL.13151618
  • GA open-source coreRocicorp marks Zero generally available and fully supported, with Apache-2.0 client and server code.14
  • Self-hosted routeDocumented deployment includes zero-cache components, PostgreSQL, application query and mutate endpoints, local replica storage, and backups.13151618

Pricing

Zero's Apache-2.0 open-source core has no separate software license fee when self-hosted; infrastructure, PostgreSQL, storage, compute, backup, observability, and operations remain the team's cost. Managed Cloud publishes fixed Hobby and Professional prices plus storage or compute additions and a BYOC price, but access is currently described as onboarding rather than full public availability.1420

Deployment estimate

Self-hosted, Hobby, Professional, or BYOC

Model PostgreSQL, zero-cache CPU and storage, replicas, backup, API servers, data size, support, additional storage or vCPU, AWS cost, and the managed-service onboarding gate.1420

Self-hosted core
Apache-2.0 client and server with infrastructure and operations owned by the team1420
Managed plans
Published Hobby, Professional, and Bring Your Own Cloud prices and resource allowances1420
Availability boundary
Core product GA; managed Cloud is onboarding and full public availability remains a roadmap item1420
Pricing checked View official pricing

Zero vs alternatives

PowerSync

Choose when
Choose PowerSync when offline-capable writes, client SQLite, or broader supported client platforms are required.
Compared with Zero
PowerSync uses a different partial-sync, mutation-backend, conflict, and Cloud billing model.124

Electric

Choose when
Choose Electric when a focused PostgreSQL read path with Shapes and an existing write API is sufficient.
Compared with Zero
Electric provides less integrated query and mutator behavior and deliberately leaves the write path to the application.78

Replicache

Choose when
Treat Replicache only as the installed source system for a migration.
Compared with Zero
It is in maintenance mode and must not be recommended for a new project.1112

Resources and sources

Official product, architecture, status, and pricing

  • Zero introduction
    Open
  • Zero project status
    Open
  • When to use Zero
    Open
  • Zero mutators
    Open
  • Zero connection and offline behavior
    Open
  • Self-hosting Zero
    Open
  • Zero open-source policy
    Open
  • Zero product and managed-service pricing
    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