v0.9 — eval gates now ship to staging

Workflows that think.

The orchestration layer for AI agents. Route between models, cache embeddings, replay any run, and ship workflows your team can actually trust.

SOC 2 Type IIEU + US regionsApache 2 control plane
requestrouterhaikusonnettoolsresponselive • routing across 4 providers

Trusted by engineering teams at

CoverbridgeHalcyonNimbus LabsStrataMosaicFoundryArdentLumen CoCoverbridgeHalcyonNimbus LabsStrataMosaicFoundryArdentLumen Co

The platform

Three primitives. Every AI workflow.

The orchestration layer your team would build if you gave them eighteen months. We did, so you don't have to.

Route between models, not around them

Send hard prompts to a frontier model, route the rest to a cheap one. Loom picks per-request based on cost, latency, and your eval gates — no hand-rolled fallback code.

run.42 · 3.2s · 4 tool calls

Replay any run, exactly

Every workflow run is recorded with inputs, tool calls, and intermediate state. Open a 3am incident in one click and step through it like a stack trace.

eval suite · 7 of 9 pass · blocks deploy

Eval gates that ship with your code

Write evals next to the prompt. Failing evals block deploys, the same way failing tests block merges. No more silent regressions when you swap models.

Observability

See every token your agents spend.

A single timeline across providers — OpenAI, Anthropic, your own fine-tunes, the cheap router you spun up last week. Filter by run, by user, by cost cliff. Tag anomalies before your bill does.

  • Per-run cost + latency + retries
  • Token-level diff between attempts
  • Slack alert on cost cliff
Explore the timeline
live - run #28401
$1.84 / hour
14:02:11sonnet412ms$0.0034ok
14:02:13haiku88ms$0.0002ok
14:02:18sonnet901ms$0.0061retry
14:02:20opus1340ms$0.0210ok
14:02:24haiku71ms$0.0002ok
14:02:31sonnet388ms$0.0033ok

Multi-agent

Hand off without losing context.

Compose agents the same way you compose functions. Loom carries the conversation, the memory, and the tool registry through every handoff — no string-passing, no fragile JSON.

  • Typed handoff contracts
  • Shared memory with TTL
  • Loop-detection built in
See the handoff API
workflow.compose
3 agents
const onboard = loom.workflow({
  research: agents.search.with({ ttl: "1h" }),
  draft:    agents.write.handoff_from(research),
  approve:  agents.reviewer.handoff_from(draft),
});

const result = await onboard.run({
  topic: input.company_name,
});
research
draft
approve
  • Typed handoff verified
  • Shared memory
  • No loops detected

Pricing

Pay for what you ship, not what you provision.

No seat fees. No volume traps. Cancel any time — your replay history stays read-only on the free tier.

Hobby

For weekend builds and ideas worth proving.

$0/mo, billed yearly
  • 10k requests / month
  • 1 workflow
  • Replay last 7 days
  • Community support
Start free
Most popular

Pro

For teams shipping to real users.

$39/mo, billed yearly
  • 1M requests / month
  • Unlimited workflows
  • Replay last 90 days
  • Eval gates in CI
  • Slack + PagerDuty
  • SOC 2 report on request
Start 14-day trial

Enterprise

For teams with auditors and SLAs.

Custom
  • Custom request volume
  • SAML SSO + SCIM
  • Replay forever
  • Dedicated VPC
  • 99.95% SLA
  • Named CSM
Talk to sales

Customers

Built by people who ship.

The teams using Loom are the ones who used to write this layer themselves.

We cut our model spend 38% in the first month after wiring Loom in front of GPT-4. The router made decisions a human couldn't make fast enough.
Priya Ramanathan
Staff Engineer, fintech
Replay turned a four-hour incident into a fifteen-minute one. I scrubbed through the run, found the bad tool call, shipped the fix.
Marcus Olafsson
Eng Manager, devtools
Eval gates in CI are the unlock. We swap models every two weeks now and the team actually sleeps at night.
Yuki Tanaka
Tech Lead, video AI
I shipped a three-agent workflow on a Tuesday. Two months ago that would have taken a sprint and a half.
Helena Voss
Founding Engineer, legal AI
Our finance team finally has a number to point at. Loom's cost dashboard pays for itself in week one.
Daniel Park
VP Engineering, SaaS
I evaluated five orchestrators. Loom was the only one where the docs matched the product.
Aisha Bello
Principal MLE, retail

FAQ

Questions teams ask before they switch.

Those are frameworks you import. Loom is a service you point your existing code at. Keep your SDK, your prompts, your tools — Loom sits in front of the providers and gives you routing, replay, evals, and observability without a rewrite.

Ship workflows that think.

Wire Loom in once. Replace your handwritten routing the next morning. Send your finance team a smaller invoice the next month.

Start free — 10k requests on us