LangGraph Platform vs Liveblocks AI Presence

“The primitive here is a managed execution runtime for persistent, interruptible graph-based agent workflows — not just a queue, not just a serverless function, but something that holds state across human-in-the-loop checkpoints. That's a genuinely hard infrastructure problem and the DX bet they've made is right: keep the graph definition in Python, offload the persistence, scheduling, and scaling to the platform. The moment of truth is deploying your first graph with streaming and checkpointing enabled, and if the CLI and SDK are as clean as the open-source LangGraph API suggests, this clears the 10-minute test. The specific decision that earns the ship is building the persistence layer as a first-class primitive rather than bolting it on — that's the part you actually don't want to build yourself on a weekend.”

“The primitive is clean: a React hook that injects an AI agent into Liveblocks' existing presence layer, giving it a cursor, a name, and a selection state — no new backend surface, no second SDK to wrangle. The DX bet is correct: they put the complexity in the abstraction, not in the integration. The moment of truth is a single `useAIPresence` call and your agent has a visible cursor within minutes. You could not replicate this on a weekend — Liveblocks' CRDT sync layer and multiplexed WebSocket infra are the actual hard part, and this just exposes a new participant type on top of it. The specific decision that earns the ship: they didn't add a new API, they extended the existing presence model — that's the right call architecturally.”

“The direct competitors are Temporal for durable execution and AWS Step Functions for managed workflow orchestration — both of which have multi-year production track records at scale. LangGraph Platform is betting that agent-graph-specific tooling (streaming tokens mid-step, human-in-the-loop interrupts, LLM-aware observability) justifies a new platform rather than an adapter on top of existing durable execution infrastructure. The specific scenario where this breaks: any team running more than a few hundred concurrent long-running agents hits pricing opacity fast with pay-per-execution, and the lock-in to LangChain's model abstraction layer becomes painful when they need to swap providers. What kills this in 12 months: AWS or Google ships a native agent execution runtime with built-in checkpoint semantics and undercuts on price, and teams realize they traded infrastructure management for vendor lock-in on a framework they already have opinions about.”

“The direct competitor here is 'just log what your AI is doing in a sidebar,' which is what most teams ship today. AI Presence beats that because the presence metaphor maps to user mental models already trained by Figma and Google Docs — a cursor is legible in a way a log entry isn't. The scenario where this breaks is any app where the AI agent operates faster than human perception — a cursor flickering across a document at 200 tokens per second is noise, not signal, and Liveblocks hasn't shown throttling primitives in the demo. What kills this in 12 months: the underlying model providers build native multi-agent orchestration UIs and presence becomes a solved layer in the stack, not a differentiator. To be wrong about that, Liveblocks would need to own enough of the collaboration infra that switching costs make their presence layer the default regardless.”

“The thesis is falsifiable: by 2027, most agent deployments will require persistent state and human-in-the-loop interruption points as baseline requirements, making stateless serverless functions a poor fit for agent hosting, and teams will pay for a runtime that understands those primitives natively. What has to go right is that agent workflows actually stabilize into repeatable production patterns rather than remaining research experiments — LangGraph Platform only becomes infrastructure if people are running agents in prod at scale, not just in demos. The second-order effect that nobody is talking about: if this wins, LangChain gains a data advantage on how agent graphs fail in production — which step, which model call, which human interrupt — and that observability data is worth more than the hosting margin. They're riding the trend of agentic workflow productionization, and they are early to the managed-runtime layer specifically, which is the right time to be.”

“The thesis here is falsifiable: by 2027, human-AI collaborative interfaces will require agents to express intent spatially, not just textually, because human coordination evolved around physical co-presence cues — gaze, gesture, position. If that's true, AI Presence is infrastructure, not a feature. The dependency is that AI agents remain slow enough relative to human attention that cursor metaphors remain meaningful; if agents complete work in under 500ms, the presence layer has nothing useful to show. The second-order effect nobody is talking about: this normalizes AI agents as social participants in software, not background workers, which shifts how users attribute responsibility and trust in collaborative outputs. Liveblocks is riding the multi-agent coordination trend and they are early — most teams haven't shipped a single agentic collaborator, let alone needed to display one. The future state where this is infrastructure: any SaaS with a collaborative canvas runs AI presence the way they run user avatars today.”

“The buyer is a platform or infrastructure engineer at a mid-to-large tech company who owns agent deployment, and the budget comes from cloud infrastructure, not AI tooling — that's actually a defensible buyer with real budget, which is the good news. The bad news is the moat: the open-source LangGraph framework is free and self-hostable, which means the platform business only works if the managed hosting delivers enough operational value to justify the margin over raw compute, and pay-per-execution pricing is notoriously hard to forecast for workflows with variable LLM call depth. What survives a 10x model price drop is the operational layer — monitoring, scaling, checkpointing — but that's exactly what AWS will commoditize. The specific thing that would change my verdict: a credible expansion story into the observability and eval layer that creates workflow lock-in beyond deployment, because right now this is infrastructure revenue with framework-level churn risk.”

“The job-to-be-done is singular and clear: make AI agent activity legible to human collaborators without building a custom observability layer. Onboarding survives the two-minute test if you're already on Liveblocks — the hook drops in and the agent appears; if you're not on Liveblocks, you're onboarding to an entire collaboration platform first, which is a different product decision. The completeness gap is real: this ships the presence primitive but not the interaction surface — users can see the AI cursor but the blog post doesn't address how users interrupt, redirect, or acknowledge agent actions, which means teams still have to build that layer themselves. The product has a clear opinion — agents are collaborators, not tools — and that opinion is the right one. Ship, but with the caveat that this is a primitive, not a complete human-AI collaboration solution, and teams should scope their expectations accordingly.”