Why AI infrastructure must evolve for agents — Akshat Bubna, CTO Modal
Modal CTO Akshat Bubna returned to the Latent Space podcast to discuss the evolution of cloud infrastructure. AI agents require fundamentally different architecture: instead of short-lived serverless functions, they need long-lived processes with state, contextual memory, and reliable scaling. Modal is building exactly that kind of platform.
AI-processed from Latent Space; edited by Hamidun News
Akshat Bubna, CTO of Modal cloud platform, returned to the Latent Space podcast after two years to discuss why the current cloud infrastructure paradigm is ill-suited for the era of AI-agents.
From Stateless Functions to Long-Lived Agents
Cloud infrastructure for the last 15 years has been built around the paradigm of short functions: a request arrives, the server executes a task in milliseconds or seconds, returns a result. This model works perfectly for web applications, microservices, and data processing.
AI-agents work completely differently. Instead of a one-off API request, an agent launches and can work for hours or days, making decisions, calling tools, analyzing results, and adapting to new information. It critically needs to maintain state, remember context, coordinate long-term plans.
- An agent does not simply call an LLM once — it iterates
- Requires a long-lived process that is not killed by the server
- Must remember the entire context between steps
- Interacts with multiple tools, APIs, and services in parallel
Why Serverless Architecture Does Not Fit
When you run a function on AWS Lambda or Google Cloud Functions, the cloud can kill the container at any moment after execution. State is not preserved. The next function call — a blank slate.
For agents, this means each iteration loses the context of previous steps. The agent cannot work long-term. Scaling becomes a problem: you run many independent functions, instead of managing a single coordinated long-lived process. Resources compete. Reliability suffers.
Current cloud platforms simply were not designed for this.
What Agent Infrastructure Requires
A platform supporting agents must provide:
- Long-lived containers that do not lose state
- Guaranteed context preservation between iterations
- Simple scaling of multiple concurrent agents
- Built-in coordination and fault tolerance
- Easy access to GPU/CPU without infrastructure management
Modal positions itself as such a platform — a cloud that first asks "what computations does the agent need?" instead of "what functions do I scale?".
What This Means
Cloud infrastructure enters its third evolution cycle. The first was about simply moving servers to the cloud. The second — microservices and function scaling. The third — is the era of long-lived AI-agents, which require a new kind of architecture. Platforms like Modal show that infrastructure must evolve together with the types of applications developers build.
- Oct 28, 2026A 2015 CNN Beat GPT-6 Astra and Claude Fable 5.1 at Skin Cancer Diagnosis
- Oct 28, 2026Google taught an LLM to “sleep”: SLEEP consolidates knowledge into weights, up to 10 million tokens
- Oct 28, 2026Keystone removes the model name from code: open-source LLM gateway adds 0.64 ms
- Oct 28, 2026Wired Tested 6 AI Agents in a Day: Dots Leads, Gemini Spark Fails at Lunch
Key Questions Answered
What are the key details on From Stateless Functions to Long-Lived Agents?
Cloud infrastructure for the last 15 years has been built around the paradigm of short functions: a request arrives, the server executes a task in milliseconds or seconds, returns a result. This model works perfectly for web applications, microservices, and data processing. AI-agents work completely differently. Instead of a one-off API request, an agent launches and can work for hours or days, making decisions, calling tools, analyzing results, and adapting to new information. It critically needs to maintain state, remember context, coordinate long-term plans. An agent doe
Why Serverless Architecture Does Not Fit?
When you run a function on AWS Lambda or Google Cloud Functions, the cloud can kill the container at any moment after execution. State is not preserved. The next function call — a blank slate. For agents, this means each iteration loses the context of previous steps. The agent cannot work long-term. Scaling becomes a problem: you run many independent functions, instead of managing a single coordinated long-lived process. Resources compete. Reliability suffers. Current cloud platforms simply were not designed for this.
What Agent Infrastructure Requires?
A platform supporting agents must provide: Long-lived containers that do not lose state Guaranteed context preservation between iterations Simple scaling of multiple concurrent agents Built-in coordination and fault tolerance Easy access to GPU/CPU without infrastructure management Modal positions itself as such a platform — a cloud that first asks "what computations does the agent need?" instead of "what functions do I scale?".
Delegate Deep Research, Coding & Multi-Step Workflows to Nomad Agent
Deploy autonomous task execution with Nomad Agent (agent.nomadnet.ai) — automated web research, data synthesis, code generation, and MCP tool orchestration.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.