How Factory scaled its cloud backend to tens of millions of daily requests on Vercel
Factory runs its full cloud backend in one Next.js app while agents deploy internal tools through Vercel APIs. The case study is useful evidence for keeping agent-operated infrastructure programmable and guarded.
Factory says one Next.js backend handles **tens of millions of daily requests** at **350ms-or-better p95** across API routes, middleware, webhooks, and log drains. Its Droids also produce **dozens of deployments a day** through Vercel APIs.
Builders should expose deployment and configuration through APIs that agents can operate, while reserving high-stakes decisions for human review. A unified backend can remain viable longer than expected if memory, duration, security, and observability controls scale with it.
Factory says one Next.js backend handles **tens of millions of daily requests** at **350ms-or-better p95** across API routes, middleware, webhooks, and log drains. Its Droids also produce **dozens of deployments a day** through Vercel APIs. Builders should expose deployment and configuration through APIs that agents can operate, while reserving high-stakes decisions for human review. A unified backend can remain viable longer than expected if memory, duration, security, and observability controls scale with it. This is a vendor case study, not an independent architecture comparison. It gives no cost profile, failure-rate data, workload distribution, or detail on the guardrails used for autonomous deployments.
This supplies scale evidence that agent-operated deployment can coexist with a unified web backend, shifting the question from whether agents can deploy to which controls make frequent production mutation governable. It reinforces observability, scoped authority, validators, and human review as operating requirements, but does not establish architecture superiority because cost, failures, workload mix, and deployment guardrails are omitted.