Deploy a LangGraph agent to production.
The LangGraph tutorial ends when your graph runs. Production is the next question: where does state live, who's allowed to call it, how do other agents reach its tools, and how do you prove what it did? a2a cloud hosts the process your graph already runs in — and adds a managed Postgres, an MCP server, an auth gateway, and a signed receipt for every run — without moving you onto LangSmith or LangGraph Platform.
your graph · managed DB · signed proof · no lock-in
'It runs' is not 'it's in production.'
A LangGraph quickstart gets you a StateGraph that executes on your laptop against an in-memory or SQLite checkpointer. Then production asks the questions the tutorial skipped — durable state, authenticated access, tool exposure over a real protocol, cost accounting, and an auditable record of every run. The usual answer is LangGraph Platform or LangSmith, which solves hosting by trading it for lock-in and a trace format you don't own.
One deploy takes the graph the rest of the way.
a2a is framework-agnostic: it deploys the whole agent app around your LangGraph code — database, MCP, gateway, frontend, receipts — so you ship to production without re-expressing your graph in anyone else's runtime.
Your graph, unchanged
Keep your StateGraph, nodes, edges, checkpointer, and tools exactly as written. a2a hosts the process — it doesn't rewrite your LangGraph app or ask you to re-express it in someone else's runtime.
Managed Postgres for state
LangGraph wants a real database for checkpoints and long-term memory. One deploy provisions a managed Postgres and wires the connection — no separate DB to stand up, no SQLite-in-a-container that vanishes on restart.
An MCP server, for free
Your graph's tools are exposed as a hosted MCP server, so other agents and MCP clients can call them over a real protocol instead of importing your Python.
OpenAPI gateway + auth
The graph gets an authenticated HTTP endpoint through an OpenAPI gateway — Keycloak-backed identity, TLS, and scoped grants — instead of an unguarded FastAPI route you bolted on yourself.
Signed receipts per run
Every graph invocation returns an Ed25519-signed receipt: inputs, tool calls, outputs, cost, caller identity, and the grant that authorized it. Observability you can prove, not just a LangSmith trace you have to trust.
Scale-to-zero microVMs
Each agent runs in a libkrun microVM that scales to zero when idle. You pay for invocations, not for a graph sitting warm on a box you rented by the hour.
Raw LangGraph deploy vs. a2a.
Frequently asked.
How do I deploy a LangGraph agent to production?
Point a2a cloud at your LangGraph project and run one deploy. It builds your graph into a libkrun microVM, provisions a managed Postgres for checkpoints, exposes your tools as an MCP server, fronts the graph with an authenticated OpenAPI gateway and TLS, and signs every run with an Ed25519 receipt. Your StateGraph code is unchanged.
Do I have to use LangSmith or LangGraph Platform?
No. a2a is framework-agnostic — it hosts the process your LangGraph app already runs in rather than a proprietary runtime. You keep observability as signed receipts you can verify yourself, so there's no LangSmith trace lock-in and no vendor holding your record of what the agent did.
Where does LangGraph state and memory get stored?
In a managed Postgres provisioned in the same deploy. Your checkpointer and long-term memory point at a durable database instead of ephemeral SQLite, so state survives restarts and scale-to-zero without you standing up or backing up a DB.
Does my graph keep working the same way?
Yes. Your StateGraph, nodes, edges, conditional routing, checkpointer, and tools run as written. a2a owns the surrounding production concerns — database, auth, MCP, frontend, receipts — so you deploy the whole agent app without re-architecting the graph.
How does scale-to-zero work for a LangGraph agent?
Each agent runs in a libkrun microVM that scales to zero when there's no traffic and wakes on the next request. You pay for invocations rather than for a warm container, which is why an idle LangGraph agent on a2a costs nothing to keep deployed.
Related guides.
All guides live in the guides index.
Ship the graph. Keep the proof.
a2a cloud deploys any agent — LangGraph, OpenAI Agents SDK, CrewAI, or custom — and ships it with a managed Postgres database, an MCP server, an API, a frontend, and an Ed25519-signed receipt for every run. Scoped grants, no ambient production access. One deploy, the whole agent app, with proof.