Superprocess superprocess.ai
Agentic workflow orchestration

Trusted agents. Governed processes.

Built for the people who own the process .

Describe a process. Superprocess runs it — agents on judgment calls, humans where it matters, every step on record.

SuperProcess Enterprise operations
Order-to-cash exception
Editing process click, drag, run
Design Run Evidence
Order in
Receive order EDI + email
Validate delivery WMS + POD
? Credit OK? gateway
Approve exception controller gate
Write back ERP + CRM
Evidence saved
Ops agent
Policy agent
Finance Controller approval request
Release order O2C-247? Policy agent found exposure within temporary limit after delivery proof
Operations
Agent
Policy
Agent
Edit process Bind agents Run workflow Human gate Evidence
Platform

Governed orchestration, not loose agents.

Enterprises need agents they can trust inside real processes.

Superprocess · platform
5 layers · one platform
L5
trace · 4 spans
Observability
Every step traced.
L4
conf 0.62 amt $28,400 APPROVE policy · threshold 0.80
Governance
Low confidence pauses for approval.
L3
class Invoice( BaseModel ) vendor: str amount: Decimal conf: float
Agents
Type-safe. Governed tools.
L2
wf-2847 resume @ event 4
Workflows
Durable. Replayable.
L1
Extract + BPMN 2.0 · 3 nodes
Process Model
BPMN your ops team reads.
Open-source foundation No lock-in on model or cloud
How it works

From process map to governed run.

Systems call services. Agents do bounded work. Humans decide exceptions. Evidence stays attached.

Invoice factoring · v3 · Draft
Saved 2m ago Deploy
AI AGENT Extract invoice AI AGENT Validate amount HUMAN TASK Review exceptions AI AGENT Policy check
5 nodes 1 human approval 3 agents
BPMN 2.0

Business analysts design in BPMN 2.0. Engineers deploy. The model compiles to the durable runtime.

  • Versioned, reviewable edits
  • Compiles directly to the runtime
Designer

Event history keeps the run intact while services fail or planners take days to decide.

  • Retries, timeouts, and human waits in one run
  • Resume from the last completed step
Durable execution

Each agent step gets its own model, tool access, and prompt — routed through human gates before writeback.

  • OpenAI, Anthropic, or private models by step
  • Only approved tools: SAP, Slack, Sheets, APIs
Agents

Exceptions and risky writebacks land in an approval queue with full context attached.

  • Approve, reject, override, or return
  • Decision owner stays on the run
Governance

Token cost, latency, and retry attribution per step — replayable for operators and audits.

  • Trace IDs join process, agent, and writeback
  • Evidence trail for executives and audits
Tracing
Where it starts

Start where the workflow already needs judgment.

Planning exceptions, document reviews, risk decisions, finance controls, and customer follow-up.

Function

Supply Chain Operations

Open full subsection

Demand & Supply Balancing

Monthly or weekly planning across forecasts, open orders, inventory, capacity.

  • signals
  • scenarios
  • planner signoff
  • exact walkthrough
Trigger and decision

Trigger: Planning cycle with changed demand, capacity, or supply

Decision: Planner chooses the scenario and tradeoff to publish

S&OP Cycle Coordination

Data aggregation across demand, supply, finance.

  • signals
  • scenarios
  • planner signoff
Trigger and decision

Trigger: Planning cycle with changed demand, capacity, or supply

Decision: Planner chooses the scenario and tradeoff to publish

Inventory Reconciliation

Cross-system matching across WMS, ERP, store systems.

  • root cause
  • owner routing
  • recovery action
Trigger and decision

Trigger: Forecast enters the queue

Decision: Scenario approval

Order-to-Cash Exceptions

Flag stuck orders, route to ops, draft customer communication with policy grounding.

  • customer promise
  • root cause
  • recovery
  • exact walkthrough
Trigger and decision

Trigger: Customer order stalls or promise date slips

Decision: Ops owner approves the recovery path

Flagship walkthrough

Watch one process move from model to decision.

Diagram, live run, human decision, and evidence trail — one process end to end.

Financial Services

Invoice Factoring Review

Process diagram

The package first branches on missing documents, then moves through extraction, buyer matching, credit policy, reviewer approval for exceptions, and funding writeback.

missing docscompleteexceptionwithin policyapproved

Operations

Invoice package

invoice, PO, POD, buyer ledger

Policy

Completeness check

required docs present?

System

Request documents

ask seller for POD or PO

Agent

Extract terms

amount, buyer, due date, tax

Agent

Buyer match

PO, receipt, terms, duplicate

Policy

Credit policy

limit, concentration, recourse

Reviewer

Credit reviewer

approve exception terms

System

Funding decision

advance rate and reserve

System

Evidence record

fields, policy, reviewer, writeback

What the diagram shows

A submitted invoice package moves through document completeness, extraction, buyer matching, concentration policy, credit approval, funding decision, and evidence capture.

250

invoice packages / day

6 -> 3

process phases

10 -> 1

people per routine deal

Workflow library

A map of the work Superprocess can own.

Recurring decision paths with cross-system context, agent work, human accountability, and inspectable evidence.

By industry

Operating queues by market.

Finance, supply chain, banking, insurance, healthcare, manufacturing, and more.

View by industry workflows
By design

Four principles every visual decision answers to.

Readable, governed, integrated, and durable before production.

01 · Calm authority

Dependable, not hype.

Restrained type and near-black ink. The tower stays legible under load.

02 · Visibility

State made visible.

Run IDs, timestamps, and agent calls in mono — marked as fact.

03 · Density without noise

Quiet surfaces, loud data.

Dense screens stay calm because type isn't competing for attention.

04 · Evidence by default

Governance means a record.

Every step, agent action, and human decision — timestamped on the run.

Pilot path

Start narrow enough to prove value and control.

Plan a pilot

Map

One workflow: trigger, owner, inputs, gates, and output.

  • Step 01

Connect

Only the documents, systems, tools, and policies for the first run.

  • Step 02

Shadow

Compare agent packets against how operators handle the work today.

  • Step 03

Control

Human approvals on exceptions. Every material decision on record.

  • Step 04
Talk to us

Tell us your workflow. We'll tell you honestly whether we can take it on.

One week shadowing your ops, then one process scoped end-to-end with human approval built in.