---
title: NoLag vs Liveblocks
description: "NoLag vs Liveblocks: Liveblocks specialises in collaborative editing with presence and conflict-free state. NoLag is general realtime messaging infrastructure with blueprint SDKs and a coordination layer for AI agents."
---

# NoLag vs Liveblocks

Liveblocks is collaboration infrastructure focused on multiplayer experiences: presence, live cursors, comments, and conflict-free shared state for collaborative editors and whiteboards. NoLag is general-purpose realtime messaging infrastructure built on pub/sub, with a collaboration blueprint of its own, plus a coordination layer built for AI agents.

Short version: if your product is a collaborative document or canvas and you want conflict-free shared state out of the box, Liveblocks is purpose-built for that. If you need realtime across many app patterns, not just collaborative editing, and you are building agentic features, NoLag is built for that.

## At a glance

| | NoLag | Liveblocks |
| --- | --- | --- |
| Core model | Realtime pub/sub over WebSocket | Collaboration primitives over WebSocket |
| Primary focus | General realtime and agent coordination | Collaborative editing and multiplayer UIs |
| High-level SDKs | Blueprints for chat, notify, feed, dashboards, tracking, collab, and more | Presence, comments, conflict-free storage |
| AI-agent coordination | Built in: dispatch, share state, observe, approve | Not a focus |
| Delivery | Presence, QoS levels | Presence, shared storage, awareness |
| SDKs | JavaScript/TypeScript, Go, Python | Client libraries and framework bindings |

## Where NoLag is different

- **General-purpose realtime.** Chat, notifications, dashboards, tracking, IoT, and collaboration are all blueprints on one platform, not a single collaboration model.
- **A coordination layer for AI agents.** Dispatch, share state, observe decisions, and gate actions with human approval, framework-agnostic and on the same infrastructure as your app features.
- **Multi-language.** First-class JavaScript/TypeScript, Go, and Python SDKs for backends, devices, and agents, not just frontend collaboration.

## Where Liveblocks is a strong fit

- Your product is a collaborative editor, whiteboard, or design tool.
- You want conflict-free shared state and awareness handled for you.
- Your realtime needs are centred on multiplayer editing.

## When to choose NoLag

- You need realtime across many patterns, not just collaborative editing.
- You are building AI-agent features and want coordination primitives.
- You want one platform for human-facing and agent-facing realtime.

## Try it

Follow the [5-minute quick start](/docs/getting-started), then look at the [high-level SDKs](/docs/high-level-sdks) and the [AI agents](/docs/agents) guide.