DoorDash’s Flux Runs 130,000 Engineering Tasks Through Cloud-Based Agents
Our take

DoorDash’s recent move to leverage its internal Flux platform for automating engineering tasks—handling 130,000 tasks in a single month and powering over 25,000 automated code reviews weekly—signals a significant shift in how organizations are approaching AI agent orchestration. This isn't merely about deploying AI; it’s about building the infrastructure to manage and scale these agents effectively. The challenges highlighted in articles like AI agents need their own identity before they need a gateway underscore the complexity. As enterprises increasingly rely on AI agents for various functions, the need for robust orchestration layers becomes paramount, and DoorDash’s implementation of Flux demonstrates a practical response to this growing demand. The reliance on isolated Firecracker microVMs, an MCP gateway, and reusable playbooks points toward a deliberate strategy for security and consistency—critical factors in a high-volume, production environment.
The architecture DoorDash has built—utilizing microVMs for isolation and a centralized auditing system—addresses a key concern: the potential for rogue AI agents to wreak havoc. Traditional agent deployments, often running directly on developer laptops, introduce significant security risks and make consistent management difficult. Moving these workloads to a cloud-based platform like Flux provides a level of control and visibility that’s simply not possible with decentralized deployments. Furthermore, the emphasis on reusable playbooks speaks to a commitment to efficiency and standardization. This approach allows DoorDash to rapidly deploy and manage new agents without requiring extensive custom configuration for each instance, something that becomes increasingly important as the number of agents grows. The broader implications extend beyond DoorDash; as noted in Orchestration is the new challenge for CX in the age of AI agents, the ability to effectively orchestrate AI agents will be a defining factor for organizations seeking to realize the full potential of AI in customer experience and beyond.
What’s particularly compelling about DoorDash's approach is its pragmatic focus on solving real-world engineering challenges. The use of multiple invocation surfaces suggests a flexible platform that can adapt to different workflows and integrate seamlessly with existing tools. This is a far cry from the often-hyped "revolutionary" AI solutions that promise the world but lack practical applicability. Instead, DoorDash has built a system that demonstrably improves developer productivity and reduces risk—a testament to the power of focusing on user outcomes over technical flash. The move also aligns with the broader trend toward capability-based AI platforms, exemplified by Cloudflare OS, as detailed in Cloudflare OS: Cloudflare's Open-Source Corporate AI Platform Built on a Capability-Based Model, where modular components are assembled to perform specific tasks, rather than relying on monolithic AI models.
Ultimately, DoorDash’s experience with Flux highlights a crucial point: the future of AI isn’t just about building smarter agents; it’s about building smarter infrastructure to manage them. As AI adoption continues to accelerate, organizations will need to invest in robust orchestration platforms that can ensure security, scalability, and efficiency. The question now becomes: will other companies follow DoorDash’s lead and build their own internal platforms, or will we see the emergence of specialized AI orchestration services catering to different industry needs? The answers to these questions will shape the landscape of AI adoption for years to come.

DoorDash has moved engineering agent workloads from developer laptops to its Flux cloud platform. The platform automated 130,000 engineering tasks in one month and supports more than 25,000 automated code reviews weekly. Flux uses isolated Firecracker microVMs, an MCP gateway, reusable playbooks, and multiple invocation surfaces to run agent workflows with scoped access and centralized auditing.
By Leela KumiliRead on the original site
Open the publisher's page for the full experience