PLATFORM · FLOW STUDIO
The visual agent canvas, owned by the people who own the process.
Flow Studio is the visual surface for designing, debugging, and deploying agents. Built for the operations analyst who knows the workflow — not the engineer who has to wire it up. Output is a versioned flow definition, not a prototype that has to be rewritten before it ships.
Built for operators, not for demos.
Most visual agent builders are demos in disguise. They ship a satisfying drag-and-drop interaction, surface a few canned templates, and leave the operator stuck the moment the workflow needs branching, retries, or a real integration.
Flow Studio is built for the operator who will own the agent in production for the next two years. Branch logic with named outcomes. Human-in-the-loop checkpoints that are real handoffs, not modal dialogs. Live preview against the same runtime as production. A test panel that mocks tools and models so the operator can rehearse failure modes before any of them happen.
The flow definition that comes out of Studio is the same one that runs in production. There is no compile step from designer artifact to engineering artifact. There is one artifact, and Studio is one of three ways to edit it.
What Flow Studio gives you.
Versioned flows
Every save creates a draft version in Registry. Production is reached only via approval. Diffs render between any two versions, including across non-consecutive edits.
Live preview
Preview executes against the same runtime that ships to production. Sandbox tools and approved test data are isolated from production state.
Human-in-the-loop checkpoints
Drop in approval steps with explicit queue, named approver groups, escalation rules, and SLA timers. Approval state lives in the run record.
Test harness
Mock any tool or model. Replay historical runs. Generate test fixtures from production traces. Export the test set to CI for regression.
The handoff to Agent Lab is a handoff, not a rewrite.
When a flow needs depth that the visual surface can't express — a custom tool, a structured prompt template, a complex retry policy — Studio hands off to Agent Lab. The handoff is at the artifact level, not the project level: the same flow definition opens in Lab, gets edited there, and shows up in Studio with the engineering edits annotated.
Operators see what changed and why. Engineers see the operator's intent and respect it. Neither team has to rewrite the other's work.
Pilot a flow on a real workload.
We pilot Flow Studio against an existing operator workflow you choose — typically a six-to-ten-week engagement that ends with one agent in your sovereign environment, owned by your operations team, governed by your Registry. No open-ended trials.