RUNTIME · CONDUCTOR
The orchestration runtime for sovereign agent workflows.
Conductor is the runtime under every Forge surface. Durable agent execution, constitution enforcement, receipt emission, residency control. Available as managed or sovereign self-hosted.
FROM PROMPT TO PROOF.
CAPABILITIES
Nine runtime primitives. One sovereign engine.
Durable execution
Agents resume across failures, deployments, and supervisor restarts.
Constitution enforcement
Out-of-scope actions refused at runtime, not in trace.
Receipt emission
Every action signs a receipt; receipts chain-anchor on settlement.
Residency control
Data, inference, and storage region-pinned per project.
Policy gates
Pre-action policy checks: PII minimisation, scope, consent, residency.
Skill resolution
Versioned, signed Skills resolved at runtime; provenance carried through.
Self-hosted mode
Run Conductor entirely on your infrastructure; receipts still settle.
Observability
OpenTelemetry-compatible; receipts are the audit-grade complement.
eIDAS 2.0 alignment
Stage 1 conformance; stage 2 in progress.
HOW IT STACKS UP
Conductor against Temporal, LangGraph, Semantic Kernel, and Bedrock Agents.
| Feature | Temporal | LangGraph | Semantic Kernel | Bedrock Agents | Forge Conductor |
|---|---|---|---|---|---|
| Durable execution | ✓ | partial | partial | ✓ | ✓ |
| Multi-agent | partial | ✓ | ✓ | ✓ | ✓ |
| Constitution enforcement | ─ | ─ | ─ | ─ | ✓ |
| Cryptographic receipts | ─ | ─ | ─ | ─ | ✓ |
| Residency primitives | ─ | ─ | ─ | partial | ✓ |
| eIDAS-aligned | ─ | ─ | ─ | ─ | ✓ |
| Self-hosted | ✓ | ✓ | ✓ | ─ | ✓ |
| Chain anchoring | ─ | ─ | ─ | ─ | ✓ |
| Open-source core | ─ | ✓ | ✓ | ─ | roadmap |
Talk to the runtime team.
If sovereignty, residency, or ZKP primitives are a hard requirement, we will scope a one-week technical evaluation.
FROM PROMPT TO PROOF.