JUST SHIPPEDRuntime 2.4 — a clearer view of every agent
CONTROLPLANE

Platform architecture

Your stack.
A clearer
operating model.

Keep the parts that make your product unique. Give the shared infrastructure a home.

Start building Book a demo

01Three layers. One system.

Built to separate concerns.
Designed to connect context.

Application layer

Your product defines the job to be done. Bring requests from application APIs, webhooks, or background workers.

Operating layer

CONTROLPLANE coordinates execution, checks policy, chooses routes, and records the decisions that matter.

Resource layer

Models, tools, and data remain replaceable. Connect them through explicit interfaces instead of hidden assumptions.

02A stable interface

Make one integration.
Keep your options open.

Describe your workload instead of hard-coding a provider everywhere. Select a routing policy, attach the relevant context, and preserve a trace ID.

  • Explicit budgets and timeouts per request.
  • Versioned routing policies for repeatable behavior.
  • Structured outputs with traceable fallback decisions.
Read the API overview
JavaScript / request contract
const request = {
  workflow: "document.review",
  input: { documentId: "doc_481" },
  policy: "production-balanced",
  limits: {
    timeoutMs: 12000,
    maxCostUsd: 0.05
  },
  metadata: { team: "operations" }
};

// Illustrative API contract.
// POST /v1/runs with this JSON payload.

03Placement with purpose

Run close to the work.
Manage from one place.

Keep regional placement explicit. Use a shared configuration model without losing sight of where a workload runs.

Americas

Customer-facing workflows with a regional execution boundary.

SAMPLE REGION / us-east-1

Europe

Dedicated placement for teams with European operating requirements.

SAMPLE REGION / eu-west-1

Asia Pacific

A regional entry point for workflows serving distributed teams.

SAMPLE REGION / ap-south-1

Regions and capabilities are fictional product examples, not active infrastructure or data-residency guarantees.

04A controlled release path

Promote with evidence.
Roll back with context.

Treat a deployment as a complete operating configuration: agent version, routing policy, tool permissions, and evaluation results.

See deployment controls

From first request to production

Infrastructure that fits.
Clarity that lasts.

Start with one workflow. Add the controls as your team grows.

Start building Talk to our team
CONTROL / CONNECT / SHIP