We've open-sourced our sync engine and dev server, released an open-source HTTP router, added new management APIs, deployed an improved realtime data engine, built a complex multi-tenant example, and optimized our documentation for AI agents.
Join thousands of companies using Liveblocks ready‑made collaborative features to drive growth in their products.
This February we open sourced new packages, alongside other improvements.
To use the latest features, update your packages with the following command.
If you were previously on Liveblocks 3.10 or below, make sure to follow our upgrade guides before updating.
This February marked a shift in how we develop at Liveblocks, moving towards an open-source-by-default approach. In the first step of this journey, we open sourced the Liveblocks sync engine and dev server, allowing you to run and test your multiplayer applications with a local Liveblocks server.
This release includes open sourcing the server that powers Liveblocks Storage and Yjs in our back end. We also have new documentation on the dev server, and how to set up Continuous Integration (CI) and End-to-End (E2E) testing.
Learn more
We also open sourced a second package in February, Zen Router, an opinionated HTTP router that’s powered Liveblocks for the past two years, handling billions of requests per month.
It features typed path params, built-in body validation, and a clean model for
auth. Here’s an example of a simple GET route handler, returning the user
returned above, and postId from the path params.
Zen Router is useful in any project that needs an HTTP router, and is compatible with Cloudflare Workers, Bun, Node.js, and every other modern JavaScript runtime.
Learn more
New Liveblocks rooms now use a completely rewritten realtime data storage engine for Liveblocks Storage and Yjs under the hood, which has a number of benefits:
We’ve been using the new engine internally since 2025, and were confident to make the switch public, which has proved seamless. No changes are required on your end—you’re already taking advantage of it.
Learn more
Enterprise customers can now access our new Management API, allowing you to programmatically manage your Liveblocks projects, API keys, and webhooks. This means you can handle dashboard operations directly from your codebase. Here’s a few examples of new APIs.
In total, 21 management APIs have been added. If you’d like to access these APIs, reach out to us to enable it on your team. Find more information in our new documentation.
Learn more
We’ve updated our Next.js Starter Kit to support multi-tenancy, using our recently released Organizations feature. With Organizations, Liveblocks resources can be fully compartmentalized into different workspaces. For example, each organization has its own set of rooms and notifications inbox.
Switching between organizations, each with its own notifications and documents
Additionally, this makes it even simpler to create share menus with workspace permissions, like you’d expect to see in modern SaaS applications.
Granting access to an organization and allowing users to edit
The Next.js Starter Kit is a realistic example of how to build a complete multi-tenant application with Liveblocks, and you can download it now to inspect it yourself.
Learn more
We’ve optimized our docs for AI, allowing agents to view a stripped down
markdown representation of any page, saving precious tokens. Agents such as
Claude Code request markdown content, and Liveblocks docs now support this.
Additionally, adding .md to the end of any page will also return markdown.
If you’d like to access our markdown docs programmatically, use the
"Accept: text/markdown" header, for example with cURL.
useThreads, useInboxNotifications, and useAiChats)
stopping pagination after the first fetchMore() call when auto-paginating in
a useEffect.client.enterRoom("my-new-room", { engine: 2 })createClient({ baseUrl: "https://..." }) to allow
connecting to the
Liveblocks dev serverLiveList performance when processing large batches of operationsLiveList.push() efficiency to prevent unbounded position string
growth over timelargeMessageStrategy client option. The WebSocket message limit
has been increased from 1 MB to 32 MB, making this setting obsolete.<RoomProvider id="my-new-room" engine={2}>...</RoomProvider><LiveblocksProvider baseUrl="https://..." /> to allow
connecting to the
Liveblocks dev serverpreventUnsavedChanges is enabled.portalContainer option from
@liveblocks/react-ui’s LiveblocksUiConfig instead of always using
document.body.enterRoom("my-new-room", { engine: 2 }).setPresence() method to set ephemeral presence for a user in a room
via the REST API, without requiring a WebSocket connectiontenantId parameter in client methods, use organizationId
instead.y-tiptap with y-prosemirror to prevent plugin key conflict, which
was causing change source to be incorrectly set in BlockNote.FloatingComposer wouldn’t auto-focus and
FloatingToolbar would conflict with it..env.local.To use these latest features, update your packages with:
Contributors include:
10 authors