Client-side sync framework in maintenance mode

Replicache

An open-sourced client-side synchronization framework for existing realtime and offline-capable web applications, now in maintenance mode.

Editorial verdict

Do not select Replicache for a new project. Keep it only as an existing-system maintenance and migration page, with current production risks documented before any move to Zero, PowerSync, Electric, or an application-owned alternative.1112

Best for

  • Existing Replicache applications that cannot migrate immediately
  • Teams documenting current push, pull, mutation, authorization, and recovery behavior
  • Migration programs that must preserve offline data and user-visible convergence
1112

Not ideal for

  • Any new project choosing a sync foundation
  • Teams requiring active feature development or a current hosted commercial service
  • Projects treating a successor as a drop-in migration without schema and protocol work
1112
Main trade-off

Existing applications can continue using a now-free open-sourced framework, but active product development has ended and migration ownership rests with the application team.1112

Product boundary

How to safely maintain and migrate an installed Replicache application, not whether to select it for a new project.

Replicache remains usable client-side sync technology, but Rocicorp states it is in maintenance mode, will receive no new features, no longer charges for use, and directs existing users toward Zero as they are able.1112

For: Teams already operating Replicache that need lifecycle support, risk control, and a deliberate migration path

  • An installed application has unsent offline mutations or client data that cannot be safely migrated.
  • The successor's write, conflict, authorization, and backend model differs materially from the current system.
  • A maintenance window, dual-run period, rollback plan, and user communication are unavailable.
  • Security, browser, dependency, or platform changes make continued operation riskier than migration.

Why teams consider Replicache

  • Existing offline behaviorInstalled applications may already rely on Replicache's local optimistic reads, writes, push, and pull behavior.11
  • Backend flexibilityReplicache was designed as client-side technology that integrates with application-owned backend stacks.11
  • Migration evidenceThe now-public code and archived repository can support maintenance and migration analysis.12

Pricing

Replicache is open-source software with no separate software license fee under its current maintenance status; the remaining cost is the existing application's backend, operations, support, and migration work. There is no current hosted commercial plan to estimate.11

Installed-system estimate

Maintenance and migration

Model current backend and support cost, protocol ownership, stored client data, unsent mutations, schema transitions, parallel operation, rollback, and migration engineering.11

Current software charge
No charge for use under the current open-sourced maintenance model11
Primary cost
Existing infrastructure, maintenance risk, migration engineering, and user-data continuity11
Pricing checked View official pricing

Replicache vs alternatives

Zero

Choose when
Evaluate Zero as Rocicorp's successor when its Postgres, TypeScript, online-write, deployment, and migration boundaries fit.
Compared with Replicache
Zero is not a drop-in Replicache replacement and does not support offline writes.111417

PowerSync

Choose when
Choose PowerSync when the replacement must preserve offline-capable client SQLite behavior.
Compared with Replicache
Its synchronization, write, authorization, and conflict architecture differs from Replicache push and pull.12

Electric

Choose when
Choose Electric when the replacement only needs reactive PostgreSQL reads and can keep writes online through an API.
Compared with Replicache
It does not preserve Replicache's offline-write contract.78

Resources and sources

Official product, architecture, status, and pricing

  • Replicache product and maintenance status
    Open
  • Archived Replicache source repository
    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