Deterministic orchestration with verifiable execution

• Orchestrate workflows as DAGs
• Execute with deterministic guarantees
• Verify every run with cryptographic proofs

Execution model

One request enqueues a run against an immutable DAG snapshot, so live edits do not rewrite historical execution.

• Submit — POST /api/workflows/run validates the graph and stores a pinned definitionHash.
• Dispatch — workers consume via Redis / BullMQ, or inline execution runs when configured.
• Observe — GET /api/runs/{id}/stream emits run and task transitions.
• Verify — proof and drift endpoints reconcile enqueue-time snapshots versus live definitions.

Quick test

Run a workflow with a single request.

curl -X POST "$BASE/api/workflows/run" \
  -H "Content-Type: application/json" \
  -d '{}'

Run lifecycle

Accepted -> Pending -> Running -> Terminal

• Accepted -> POST /api/workflows/run
• Running -> GET /api/runs/{id}/stream
• Terminal -> Proof APIs

Each state corresponds to observable API operations.

Typical usage flow

Client -> POST /api/workflows/run -> Execute -> Stream -> Verify

Next step

Ready to execute against live endpoints?

Explore API ->