How Factory scaled its cloud backend to one billion monthly requests on Vercel
Factory runs API routes, middleware, and webhooks in one Next.js backend at one billion daily requests and 350ms p95. Its agents also deploy internal tools through Vercel APIs under review guardrails.
Factory says one Next.js backend handles **one billion daily requests** across API routes, middleware, and webhooks at **350ms p95 or below**. It tuned memory limits and function duration rather than creating separate backend infrastructure.
Agent-heavy teams can keep deployment APIs behind explicit guardrails: Factory's Droids configure, build, and deploy internal tools, while engineers review high-stakes decisions. Observability and route-level WAF rules cover abusive traffic.
Factory says one Next.js backend handles **one billion daily requests** across API routes, middleware, and webhooks at **350ms p95 or below**. It tuned memory limits and function duration rather than creating separate backend infrastructure. Agent-heavy teams can keep deployment APIs behind explicit guardrails: Factory's Droids configure, build, and deploy internal tools, while engineers review high-stakes decisions. Observability and route-level WAF rules cover abusive traffic. This is a vendor case study, not a reproducible benchmark. The material also contains a conflicting quote about tens of millions of daily requests and does not provide workload, cost, or reliability distributions.
This revises the earlier Factory scale claim upward while weakening confidence in the number: the title says monthly, the brief says daily, and the material also retains a tens-of-millions figure. It still reinforces the prior operating pattern—a unified programmable backend with review, observability, and traffic controls—but remains evidence of feasibility, not architectural superiority or a reproducible benchmark.