Liveblocks: Collaboration Backends with Presence, Storage, Comments, and Notifications

🌏 中文版

Liveblocks is a managed collaboration backend. Rooms commonly represent documents, whiteboards, workflows, or other artifacts and expose Presence, Broadcast, Storage, Threads, and Feeds, plus editor and Yjs integrations, comments UI, mentions, and notifications.

Separate ephemeral Presence from durable Storage

Presence holds per-connection cursor, selection, and status JSON and resets after disconnect. It is not document content or permanent membership. Broadcast carries non-persistent room events. Storage persists conflict-free structures for shapes, nodes, or cells, while text editors can use a Yjs provider. Merge semantics differ by type: concurrent writes to one LiveObject property may use the last modification received by the server. “CRDT” does not mean every semantic conflict disappears.

Comments and Threads, mentions, and Notifications support asynchronous product collaboration. They retain user IDs rather than copying entire user profiles, so applications provide resolvers. Thread visibility, room permissions, and notification recipients must agree, especially for private comments and workspace isolation.

Product boundaries still determine authorization

Production backends should use a secret key to issue ID tokens; public keys are for prototypes or public apps. ID-token mode can make room default, group, and user access the authorization source. Access-token mode leaves each issuance dependent on the application's canonical ACL. Apply least privilege across *:read/write and storage, comments, and feeds scopes. Room IDs are not secrets.

Liveblocks retains realtime Storage, Yjs documents, comments, and some webhook data. Verify region, retention, deletion and export, encryption, backup expectations, webhook retry, and residency. If the application database remains canonical, define Liveblocks as source, cache, or collaboration projection and handle synchronization failure through webhooks and an outbox.

Liveblocks fits products needing multiplayer cursors, shared state, comments, mentions, inboxes, and editor integrations quickly. Yjs is a CRDT engine with selectable providers; Ably is lower-level messaging; PartyKit and Durable Objects run custom room servers. AI agents need distinct IDs, expiring presence, minimal write scopes, attributable actions, and human override.

References

• Liveblocks concepts
• Authentication
• Permissions
• Liveblocks client: Presence and Storage
• Liveblocks Yjs provider
• Data storage