▸ Browse docs — Guides
▸ SECTION C · Guides
Import from LangGraph
Last updated: 2026-08-16
Orkena is not a LangGraph competitor — it is the substrate LangGraph graphs get deployed onto when governance becomes the requirement. The adapter imports existing workflows as first-class graphs.
What carries over
| LangGraph concept | Orkena equivalent |
|---|---|
| StateGraph / nodes | Graph nodes (agent, tool, transform, router, terminate) |
| Edges and conditional edges | Edges; conditional routing becomes router nodes |
| Tool nodes | tool nodes via MCP |
| Human-in-the-loop interrupts | gate.hitl nodes |
| Checkpointer | The durable executor’s checkpoints |
What doesn’t carry over
- Custom runtime code that bypasses the executor — runs inside Orkena use the durable engine
- Tools that are not MCP-compatible — wrap them or use the tool adapter
- Framework-specific lifecycle hooks — replace with transform nodes
How to import
- Export your graph from LangGraph as JSON (or point the adapter at the source file).
- Import in Orkena: Graphs → Import → LangGraph.
- Review the mapped graph in the canvas; adjust node types where the mapping is approximate.
- Wrap in governance: attach the baseline-security policy pack, add
gate.hitlwhere approvals are required, and enable ledger capture. - Publish the first version and run it.
What you gain
The imported graph now runs on the durable executor with policy on every edge, a hash-chained ledger, deterministic replay, and evidence bundles — none of which require rewriting your logic.
Was this helpful?