Factory raises $200 million at a $5 billion valuation

Factory’s announcement says the enterprise coding-agent company raised $200 million at a $5 billion valuation, more than tripling its $1.5 billion valuation from about five months earlier. The round takes total funding above $400 million and will finance research, product development, and global sales and deployment.

An April report placed Factory’s previous round at $150 million and its valuation at $1.5 billion. The latest announced valuation is 3.3 times that figure. Factory has not disclosed current annual recurring revenue or detailed financing terms.

Blackstone is buyer and backer

Blackstone participated in the financing and appears on Factory’s customer list, giving the investment firm exposure as both a shareholder and a buyer. Eight other institutional investors joined the round:

• Khosla Ventures
• Sequoia Capital
• Insight Partners
• Evantic Capital
• Sound Ventures
• NEA
• Mantis VC
• Clearlake

Nico Rosberg, Brad Gerstner, and Salesforce chief executive Marc Benioff also invested as individuals.

Droid reaches from plan to release

Founders Matan Grinberg and Eno Reyes started Factory in 2023 to automate work across the software development lifecycle. Its Droid agent can plan tasks, write and review code, and ship changes within the permissions and workflows configured by an engineering team.

Factory positions Droid as part of a governed enterprise system. Administrators choose which models handle particular tasks, where workloads run, and how agent activity is measured. The company describes the system as self-improving, though it has not detailed whether that learning changes prompts, routing policies, evaluations, model weights, or another layer of the stack.

Factory names Nvidia, Blackstone, Royal Bank of Canada, Palo Alto Networks, Adobe, and T-Mobile as customers. Those references span banking, telecommunications, security, and software, where code handling, auditability, and deployment boundaries can shape purchasing decisions. Contract sizes and the extent of production use remain undisclosed.

Deployment carries the pitch

Factory’s enterprise strategy centers on a control layer that can operate in the cloud, on premises, or within an air-gapped environment isolated from the public internet. Recent product releases support that approach:

• Factory 2.0 organizes agents into coordinated workflows across the development lifecycle.
• Factory Router selects a model for each task according to cost and performance requirements.
• Deployment configurations target air-gapped, regulated, and public-sector environments.
• Agent Effectiveness connects agent usage and spending with measures of delivered code.

Factory says its router reduces token spending by more than 60% while preserving performance. Routing can send routine work to a cheaper model and reserve more expensive models for harder tasks. The resulting savings depend on the workload mix, model prices, routing accuracy, and the evaluation used to define a successful result.

Air-gapped deployment can keep source code and execution inside a controlled network. Buyers evaluating Factory’s FedRAMP-oriented offering should confirm its current authorization status, covered services, external dependencies, logging behavior, and model endpoints.

What the valuation assumes

Factory said during its April financing that revenue had doubled month over month for six consecutive months. The company did not publish the starting revenue base, current recurring revenue, customer retention, or gross margin, leaving the scale and durability of that growth unclear.

Factory competes for enterprise development budgets with Cursor, Cognition, Anthropic’s Claude Code, and OpenAI’s coding products. Its stated differentiation rests on model choice, deployment flexibility, governance, and measurement across large organizations. The new capital can support the security reviews, integrations, sales teams, and customer support required for those deployments.

A $5 billion valuation places weight on Factory converting customer trials into broad production use while controlling inference and implementation costs. Changes in model quality and pricing could strengthen its routing economics or reduce the value of a separate orchestration layer.

A rollout checklist for engineering teams

1. Map the deployment boundary. Confirm which components run in Factory’s cloud, a private environment, an on-premises installation, or an air-gapped network. Identify any telemetry, update, or model endpoint that crosses that boundary.
2. Trace data handling. Document how source code, prompts, logs, embeddings, and generated output are stored, retained, and used. Clarify what “self-improving” means for proprietary data.
3. Review agent permissions. Test repository access, branch protections, CI/CD integration, approval gates, audit logs, rollback procedures, and limits on production actions.
4. Evaluate the router. Benchmark representative tasks across supported models, inspect fallback behavior, and determine whether teams can pin model versions or override routing decisions.
5. Calculate total cost. Include licenses, token usage, infrastructure, implementation, security review, and support. Compare Factory’s claimed token savings against the organization’s own workload.
6. Measure production outcomes. Track accepted changes, review time, defect rates, deployment frequency, incident rates, and developer time saved alongside generated-code volume.

The missing numbers

Factory has yet to publish current annual recurring revenue, pricing, gross margin, paid production deployments, or the methodology behind its 60% token-spending claim. Clearer definitions of self-improvement, customer data isolation, and government authorization would also help technical buyers assess the platform. Those figures will determine whether the financing reflects durable enterprise adoption or expectations that still need operating evidence.