{"id":524315,"date":"2026-06-08T09:08:11","date_gmt":"2026-06-08T09:08:11","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/524315\/"},"modified":"2026-06-08T09:08:11","modified_gmt":"2026-06-08T09:08:11","slug":"zero-reaches-1-0-marking-the-first-stable-release-of-rocicorps-web-sync-engine","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/524315\/","title":{"rendered":"Zero Reaches 1.0, Marking the First Stable Release of Rocicorp’s Web Sync Engine"},"content":{"rendered":"

Rocicorp<\/a> has shipped Zero 1.0<\/a>, the first stable release of its general-purpose sync engine for the web, arriving after nearly two years of development, more than 50 releases, thousands of commits, and hundreds of bugfixes. The milestone signals that Rocicorp now fully supports the Zero API and is committing to maintaining it, with any future breaking changes expected to be rare and far smaller than those seen during the alpha period.<\/p>\n

Functionally, the release notes<\/a> describe 1.0 as a very minor update to the previous 0.26.2 build, with the major version bump being largely symbolic and carrying no actual breaking changes. The headline addition is a schema change hook that detects publication changes on Supabase<\/a> through COMMENT ON PUBLICATION statements, working around Supabase’s lack of event trigger support for publications. The release also bundles fixes for corrupted litestream restores, error handling when change data capture is unhealthy, an IPC_CHANNEL_CLOSED race condition during shutdown, orphaned subscriber scenarios, and time and timetz SQL generation.<\/p>\n

Zero works by pairing a zero-client library inside the app with a zero-cache service that maintains a read-only replica of a Postgres database. Queries written in ZQL, Zero’s streaming query engine<\/a>, run against the local cache first and return matching results in the next frame, while authoritative results sync from the server in the background. Founder Aaron Boodman has argued on Hacker News<\/a> that this bring-your-own-database approach is a strength, noting that Zero is “just a fancy cache” that cannot corrupt data and lets teams adopt it incrementally or move off it easily.<\/p>\n

Community reaction has been positive on developer experience but more cautious on production readiness. Reviewing the engine, Marmelab<\/a> found that it delivered on speed and developer experience while flagging some notable limitations:<\/p>\n

<\/p>\n

\u2026some limitations can still be significant, depending on the complexity of the app you want to build and the tech stack you want to use. Here are some examples we noted:<\/p>\n


\n <\/p>\n