Warp Factories | Warp

Introducing Warp Factories

Benchmark. Optimize. Repeat.

Benchmark on Your Own Work

Replay historical tasks from your factories to measure performance against your team’s real workflows.

Measure What Performs Best

Compare models, harnesses, and configurations across quality, correctness, efficiency, and custom scorers.

Put the Results to Work

Update your factory code to route work to the best-performing setup.

Learn more about benchmarks

Early Access

Request Early Access

Set up your first factory with early access.

Get up to $10,000 in free factory usage

SDLC Coverage

Beyond CI/CD to Automating the Whole SDLC

Defined in code, built for scale, and easy to deploy.

Opinionated, but Flexible

Set up your first factory in 5 minutes, build it out over time.

Factories as Code

Repos, agents, models, permissions, and checkpoints in one definition.

# factory.yaml
schemaVersion: v1alpha1
name: pr-review
repositories:
  - owner: acme
    name: web
agentDefaults:
  model: claude-5-fable-high

# agents/foreman/agent.md
agentType: FOREMAN

# agents/review/agent.md
agentType: REVIEW
model: glm-5.2-fireworks

# automations/on-pr/automation.md
agent: review
triggers:
  - provider: github
    event: pull_request_ready

API, CLI, SDK and MCP

Built as a platform, not a vertical product or AI teammate.

# cli
$ warp agent run-cloud --environment ENV_ID \
    --prompt "fix LIN-482, low risk only"

# api
$ curl -X POST https://app.warp.dev/api/v1/agent/runs \ 
    -H "Authorization: Bearer $WARP_API_KEY" \ 
    -H "Content-Type: application/json" \ 
    -d '{ "prompt": "fix LIN-482" }'
{ "run_id": "run_4026", "state": "QUEUED" }

How Work Moves Through a Factory

Issues land from the channels your team already uses, the foreman moves them down the line, and the line stops wherever you decide.

  1. Triage: optional cause, scope, a tracked issue — skipped when the ask is clear
  2. Spec: optional the plan for how the change should land — skipped for small, clear work
  3. Implement: writes the code and tests, opens a pr
  4. Verify: adversarial review, evals, and checks
  5. Ship: the approved change lands
  6. Monitor: watches prod, files what it finds

Case Study

Cutting Our Cost per PR from $80 to $30

How we used Warp Factories Benchmarks to test models on our own engineering tasks and optimize for cost without sacrificing quality.

Open at Every Layer

Layer 01 Any Agent: any MCP-capable coding agent.

Layer 02 Any Model: chosen per pipeline stage.

Layer 03 Your Compute or Ours: warp's cloud, or self-hosted in your own VPC.

Layer 04 Data Lives Where You Want: you own and store what your factory produces.

Baked-in Measurement and Self-Improvement

Evaluations, benchmarks, and self-improvement loops drive measurable gains.

Control Your Coding Agent Chaos

Continuous improvement, better governance and security, by default.

Increase Agent ROI · Cost per PR

$18.09 -33% may 20

Frequently Asked Questions

What is a cloud software factory? A factory is a fleet of agents wired to your SDLC — triggered by an issue, a slack message, or a schedule, and coordinated by Warp Factories from triage through review to a mergeable PR.

How do I define a factory? As code, in a factory.yaml + supporting agent files. Define triggers, agents, models, and approval gates — check it into your repo like any other config.

Do I have to use Warp's models or config? No. Bring your own model or harness (e.g., Claude Code or Codex) — Warp Factories work with whatever your team prefers and helps identify the most cost-effective configuration over time.

Do I need Warp Terminal to use factories? No. Factories is a separate product — nobody at your company has to use Warp Terminal. Work comes in through tools you already use, like Slack, Linear, Jira, GitHub, and GitLab. If you do use Warp Terminal, it has built-in factory integrations (native MCP) so you can iterate locally.