sqlsync vs yjs-cf-ws-provider
Collaborative data projects compared
sqlsync helps web applications share SQLite state across users and devices, including offline, with reactive queries and collaborative updates. yjs-cf-ws-provider relays Yjs collaboration over WebSockets on Cloudflare; it is presented as a learning and demonstration project rather than a production-ready service.
sqlsync: Synchronize Collaborative SQLite State Offline
SQLSync wraps SQLite to let web applications share database state across users, devices, and the edge, including during network interruptions. It suits teams building local-first apps that need reactive queries and collaborative updates.
yjs-cf-ws-provider: Relay Yjs Collaboration over Cloudflare
A serverless WebSocket provider that relays Yjs updates using Cloudflare Workers and Durable Objects. Intended for learning and demonstrations, it supports Yjs WebSocket clients and can persist document state to R2.
| sqlsync | yjs-cf-ws-provider | |
|---|---|---|
| Language | Rust | TypeScript |
| License | Apache-2.0 | MIT |
| Stars | 2.9k | 32 |
| Forks | 42 | 5 |
| Last analyzed | Oct 4, 2026 | Oct 3, 2026 |
Key differences
- sqlsync centers on shared, eventually consistent SQLite state; yjs-cf-ws-provider relays collaboration messages for Yjs clients.
- sqlsync describes offline-first use, optimistic reads and writes, and reactive query subscriptions; yjs-cf-ws-provider focuses on WebSocket connections and periodic document-state persistence to R2.
- sqlsync is written in Rust and licensed under Apache-2.0; yjs-cf-ws-provider is written in TypeScript and licensed under MIT.
- sqlsync includes a React library and cross-tab synchronization; yjs-cf-ws-provider includes a local demo app with a TipTap editor and supports the Yjs WebSocket Connector.
- sqlsync is intended for building collaborative applications around SQLite; yjs-cf-ws-provider is aimed at learning, prototyping, and demonstrating Cloudflare Workers and Durable Objects.
- yjs-cf-ws-provider recommends PartyKit for production use; sqlsync's considerations focus on SQLite data modeling, eventual consistency, shared-worker debugging, and one-statement execute calls.
Choose sqlsync if you…
- need collaborative application state represented in SQLite.
- want offline-first use with optimistic reads and writes or reactive query subscriptions.
- need cross-tab synchronization or a React library for a web application.
Choose yjs-cf-ws-provider if you…
- want to prototype a Yjs collaboration relay using Cloudflare Workers and Durable Objects.
- need a provider compatible with the Yjs WebSocket Connector for client testing.
- want a learning or demonstration project that includes WebSocket Hibernation and R2 persistence.
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.