Platform
Eight capabilities make up the Forge platform. They are designed to be used together, but each one is addressable on its own through the API — so you can adopt the platform incrementally instead of all at once.
Intelligence steps with typed inputs, structured outputs and evaluation attached from day one.
Durable execution for processes measured in days rather than milliseconds.
Governed access to the records a workflow needs, without copying your warehouse.
Typed connectors that fail loudly when an upstream contract changes.
Everything in the console is an API call, documented and versioned.
Outbound delivery you can trust, and a replay button for when you cannot.
Roles that map to how the team is actually organised.
Cost, latency, throughput and accuracy — attributed to the step that caused them.
Runtime
A Forge run is a state machine with a durable log. That single design decision is what makes retries safe, audits complete and long-running processes possible.
Input is validated against the workflow schema and assigned a run identifier.
The engine resolves the step graph for the pinned workflow revision.
Steps run with checkpoints; failures retry with backoff instead of restarting the run.
Low confidence or a hard failure routes the run to the assigned review queue.
Writes happen behind idempotency keys, then the audit event is sealed.
forge / api console
POST /v1/workflows/invoice-intake/runsauthorization: Bearer sk_live_••••••••idempotency-key: inv-2026-08-17-0091 200 OK 142ms{ "runId": "run_9f21ac", "status": "completed", "steps": 6, "reviewed": false}Demo figures shown to make the template concrete. Replace with your own numbers.
Adjacent
The product overview shows these capabilities in the context of a real workflow. The security page covers the control model in detail.
Get started
Most teams start with a single workflow and one connector. The platform is designed so that first step does not become a rewrite later.