// the find
liveblocks/liveblocks
Realtime infrastructure for multiplayer apps and agents
Liveblocks is a hosted realtime collaboration backend — think presence, cursors, comments, CRDT sync, and now AI agent participation — all as a managed service you wire into your React app. It's for product teams who want Google Docs-style multiplayer without building the WebSocket infrastructure themselves. The SDK depth is real: first-class integrations with Tiptap, Lexical, BlockNote, Yjs, Redux, and Zustand.
1. The Yjs provider is genuinely useful — you get CRDT conflict resolution plus Liveblocks' presence and auth layer without running your own y-websocket server. 2. The text editor integrations (Tiptap, Lexical, BlockNote) include server-side node packages for SSR and document-level operations, not just client wrappers — that's the hard part done. 3. AI agent participation is a real feature, not a marketing label: agents can join rooms, hold presence, and stream responses in a way that's indistinguishable from a human participant to the client SDK. 4. Notification batching with email templating via @liveblocks/emails means comment threads can send digests without you wiring together a separate notification system.
1. It's a managed service with a free tier ceiling — self-hosting is not an option, so your production app has a hard dependency on Liveblocks' uptime and pricing decisions you can't control. 2. The dual-license (Apache-2.0 + AGPL-3.0) split isn't clearly documented in the README; AGPL components could be a problem for closed-source SaaS without a commercial agreement. 3. The React-only client story is well-developed, but Vue, Svelte, and vanilla JS support lag behind — the Redux/Zustand adapters help but feel bolted on compared to the React hooks experience. 4. Room-based data model means anything that needs cross-room queries (global notifications, user-level history) requires you to call the REST API separately — the SDK doesn't abstract this gap.