QUANT Flow
Work you can see running
Flow turns repeatable work into a graph: agents, tools, conditions, branches and human approval. The picture is the program — what you see is what executes.
Designed around the things that go wrong
Versioned definitions
A flow is published as a version. A run records the version it used, so a change today cannot rewrite what happened last week.
Durable runs
A run does not depend on one request staying alive. State is written down, so it can pause, wait and continue.
Approval steps
A human gate anywhere in the graph. The run waits, and nothing downstream happens until someone answers.
Careful retries
Reads and timeouts retry. Sending, publishing, paying and deleting do not — a retry there is a duplicate, not a recovery.
Inspectable
Every node shows completed, running, waiting, failed or skipped, with its inputs, duration and cost.
Cancel and resume
Stop a run mid-flight, or continue one that stopped for a person.
Status: Flow is in development. The runtime foundations it depends on — durable runs, approvals and budgets — are in beta today. We will not ship a canvas that draws a graph the engine does not actually run.