Warp wants to make it easier to build your software factory

Warp has a new pitch for the people already trying to automate more of software development: don’t build the whole factory yourself. On Tuesday, the company introduced Warp Factories, which it describes as open infrastructure for cloud software factories — agentic systems that handle work across the software development lifecycle.

The idea is simple enough. Warp says the infrastructure gives developers the building blocks to assemble their own scalable factories, without forcing them to give up flexibility, programmability, customization, or ownership. Founder and CEO Zach Lloyd says the point is to take care of the annoying parts so teams can focus on tuning the factory for a specific product.

He’s also aiming at two headaches that come up fast once coding agents enter the picture: proving return on investment and keeping control over what the system is doing. Warp Factories includes queryable metrics on throughput, cost, quality, and ROI through the Factory control room, API, and Factory MCP. It also adds evals, benchmarks, self-improvement loops, and memory. Scorers can judge how work items move through the system, looking at token spend, code quality, and whether defects were introduced. Then “observer” agents can score runs, look for ways to improve them, and even make pull requests that change the harness, model, or context.

Governance is part of the sales pitch too. Warp says factory definitions live as version-controlled code, alongside distinct agents, skills, MCPs, and permissions. But the governance problem, as Lee Faus of Atomic Software puts it, is bigger than just deciding what an agent is allowed to do. He argues the harder question is whether a company can prove what the system actually did, later, when a chain of humans and agents has touched the same change.

That caution runs through the reactions Warp got. Faus says software factories are probably inevitable, but not yet ready to become as foundational as CI/CD. Erik Gfesser, another engineer quoted by The New Stack, also thinks organizations shouldn’t try to build all of this in house. Even so, he expects adoption to be slow and fragmented across vendors, much like early CI/CD. Warp’s client is open source, but its server, Warp Drive backend, and OZ orchestration layer are proprietary. OpenAI is listed as the founding sponsor of Warp’s open source repository.