Skip to content
Product

The AI Agent Control Plane.

Enforce policy, require approval, and retain decision evidence for actions routed through Cordum.

Safety Kernel: Pre-Execution Governance.

The policy decision point for governed submissions. A denied submission is not dispatched.

  • Inline Policy
    Decision before dispatch
  • Human Gates
    Approval required for risky work
  • Constraint Logic
    Budgets, deny-paths, limits
  • Policy Simulation
    Test rules before they go live
safety-policy.yaml
rules:
  - name: prod-write-approval
    match:
      risk_tags: [prod, write]
    decision: REQUIRE_APPROVAL
    reason: "Production write detected"

  - name: kubectl-constraints
    match:
      capability: kubectl
    decision: ALLOW_WITH_CONSTRAINTS
    constraints:
      deny_paths: ["/kube-system/*"]
      max_runtime: 300s
incident-response.yaml
name: triage
steps:
  collect:
    type: worker
    topic: job.sre.collect
  
  approval:
    type: approval
    depends_on: [collect]
    
  remediate:
    type: worker
    topic: job.sre.patch
    depends_on: [approval]

Workflow Engine: DAG Orchestration.

Coordinate complex multi-agent sequences with explicit dependencies, retries, and failure semantics.

  • DAG Execution
    Parallel step orchestration
  • Schema Validation
    I/O contract enforcement
  • Saga Rollback
    Automatic undo on failure
  • Run Timeline
    Append-only audit records

Scheduler: Intelligent Routing.

The scheduler that knows when to stop. Least-loaded worker selection with capability-based routing and overload protection.

  • Least-Loaded
    Optimal worker scoring
  • Capability Filter
    Route to specialized tools
  • Backpressure
    Avoid worker exhaustion
  • Reconciler
    Detect and mark stale jobs
// Least-loaded scoring
score = active_jobs + (cpu_load/100) + (gpu_util/100)
// Capability filtering
job.requires = [kubectl, gpu]
worker.capabilities = [kubectl, s3, net:egress]
→ Capability Mismatch
Go
Statically linked binaries
NATS
Durable JetStream events
Redis
Pointer-based state store
Protobuf
Strict wire contracts

Backbone: Customer-Managed Infrastructure.

Go services with NATS and Redis dependencies plus documented deployment controls. Validate availability, capacity, and security in your environment.

  • At-least-once delivery with NATS JetStream
  • Per-job locks for strict idempotency
  • Dead Letter Queue (DLQ) for failed actions
  • Prometheus-native metrics and structured logs

Packs: Extensibility Reimagined.

Apply declarative configuration overlays for workflows, schemas, and policy without changing the core control plane. Deploy worker binaries separately.

  • Declarative pack.yaml for metadata and topics
  • Bundle schemas, workflows, and policy overlays
  • Verify pack integrity before installation
  • Soft uninstall preserves data while disabling routing
Explore Pack Docs
API
Pack structure
pack.yaml
Declared
workflows/
Declared
schemas/
Declared
overlays/
Declared

Enterprise Governance

Licensed identity, role, audit-export, and contracted support entitlements for customer-managed deployments.

SSO / SAML
Advanced RBAC
SIEM Export
FAQ

Common questions

Answers about the Cordum control plane.

What is the Cordum Safety Kernel?+

The Safety Kernel evaluates governed job and action submissions before dispatch. It checks policy bundles, returns Allow, Deny, Require Approval, or Allow with Constraints decisions, and records decision metadata through configured audit paths.

How does Cordum differ from agent frameworks like LangChain or CrewAI?+

Agent frameworks handle task execution and LLM orchestration. Cordum adds a control plane for policy decisions, approval gates, and decision evidence. Published adapters cover selected frameworks, and custom integrations can use the CAP protocol directly.

Is Cordum open source?+

Cordum is source-available under the BUSL-1.1 license. Available features and commercial rights depend on the selected tier and license terms; see the current pricing and licensing pages for details.

What protocols does Cordum support?+

Cordum uses the Cordum Agent Protocol (CAP v2) as its wire format and supports MCP (Model Context Protocol) in both standalone stdio and gateway HTTP/SSE modes.

Can Cordum run on-premises?+

Yes. Cordum is designed for self-hosted deployment. Run it locally with Docker Compose or deploy to any Kubernetes cluster. There is no mandatory cloud dependency.

Ready to add policy to your agents?

Follow the documented quickstart and validate the stack locally in your environment.