Modal Raises $750M Series D for AI Execution Infrastructure

The engineers at Modal took a central database out of the route an agent follows to get a computer. For the New York AI infrastructure company, co-founded by CEO Erik Bernhardsson and CTO Akshat Bubna, that scheduling decision helps explain the business behind its latest financing: developers can ask for an environment through code, while Modal takes responsibility for making the request work across a large fleet.

Modal announced a $750M Series D on October 14, 2026, led by Accel at a $15.75B post-money valuation. Kleiner Perkins joined the round alongside existing investors. The financing supports a platform spanning model training, inference and isolated environments where agents can execute code, giving Modal several routes into the infrastructure budget of an AI application.

The company reports crossing $1B in annualized run rate, including a $300M pace for its Sandboxes product. Those figures describe the current pace of the business, rather than revenue already earned over a full year. The interesting commercial development is how much of an application's working environment now travels with the agent.

What Modal's Series D adds to its funding history

Accel's investment account confirms that the firm led the $750M financing, deepening its earlier investment. Modal names Menlo Ventures, General Catalyst, Redpoint, Lux Capital, Amplify Partners and Bain Capital Ventures among the existing investors participating. The announcement establishes the round and its post-money valuation without disclosing individual check sizes or a detailed spending budget.

Modal's previous Series C announcement, dated May 21, 2026, disclosed $355M at a $4.65B post-money valuation. General Catalyst and Redpoint led that round, while Menlo, Bain Capital Ventures and Accel joined as new investors. Accel has moved from joining the syndicate to leading the next financing in roughly 5 months, a concrete change in its financial relationship with the company.

Modal now says it has raised over $1.2B in total. The company reports that usage has tripled since the Series C and that growth has exceeded 15x year over year; those operating figures remain company-reported. The capital provides resources for continued infrastructure and product development as customers ask the same supplier to support a wider range of work. The announcement gives no allocation percentages, infrastructure purchase commitments or separate acquisition budget, so the financing should be read alongside the products Modal is already putting into customers' hands.

Why an agent needs its development environment

An agent assigned a software task may have to run the application, inspect a database and test a change against several connected services. Modal's Sandbox documentation describes environments for executing arbitrary user or agent code, with configurable images, storage and commands. That places the runtime inside the quality of the result: the environment determines what the agent can actually execute and observe.

Modal made VM Sandboxes generally available on October 1. These environments supply a Linux kernel and support workloads needing Docker, local databases and capabilities that a lighter container environment may not provide. Modal keeps both gVisor and VM runtimes available; the right choice depends on the workload. Its documentation currently limits GPU Sandboxes to gVisor, a useful distinction for teams combining code execution with accelerated compute.

The customer examples give the product a recognizable place in an engineering organization. Modal says Linear's Coding Sessions put a user's development environment inside a VM Sandbox. Legora uses the environments to evaluate legal agents against an application that includes Postgres and a document editor. These are vendor-published deployment accounts, but they make the purchasing decision tangible. A team choosing an agent environment is also choosing how much of its existing application can accompany the software into the task, and how much setup its own engineers must continue to maintain.

The engineering hidden behind a simple compute request

Modal's sandbox scaling account describes why the company rebuilt its scheduling system. Central coordination and writes to a shared database had become difficult to carry through very high rates of environment creation. The redesign lets scheduling servers use cached state and contact workers directly, with much of the durable recordkeeping handled asynchronously.

In Modal's account, each worker becomes the authority for its own state, and scheduling behaves more like distributing requests across available machines. This is a specific engineering trade-off behind the apparent simplicity of asking for another Sandbox. It also helps explain why the founders invested in infrastructure below the API: a developer's short request can trigger a substantial amount of coordination that the customer never sees.

Modal reports demonstrating 1M concurrent Sandboxes in its engineering test. A benchmark describes the conditions tested, while a customer's deployment still has its own capacity, startup and reliability requirements. The company's platform description identifies a custom file system, container runtime, scheduler and image builder, with usage-based pricing. That commercial model ties Modal's opportunity to work actually running on its platform. For customers, the evaluation extends from whether the API is pleasant to use to how the platform behaves when many agents need environments at once, with real dependencies and a delivery deadline attached.

Model changes bring another operating decision onto Modal

Execution is only one part of Modal's expanding role. Its Endpoint Candidates release, announced October 12, lets teams stage alternative inference deployments and mirror a sample of production traffic to them. Teams can inspect latency and throughput, run their own quality evaluations and promote a candidate while retaining the production endpoint URL.

The original deployment continues answering users during evaluation. Modal also explains that mirrored requests are best-effort and may be dropped under pressure, protecting the original production request from a slow candidate. That behavior matters when interpreting results: evaluating a model inside an application involves traffic handling and resource limits as well as the model's output.

Together, Sandboxes and Endpoint Candidates put Modal near two recurring decisions: what an agent can run, and which model deployment should serve customers. The commercial attraction is continuity across experimentation and operation, with the same supplier carrying more of the infrastructure work as an application changes. Customers still have to judge cost, isolation, dependencies and service behavior against their own workloads. A team promoting an inference candidate has a very particular decision in front of it: whether the measured change is good enough to become the response its users receive, on the environment Modal is now being paid to keep running.