Baseten Acquires Blaxel to Add Agent Execution to Its AI Infrastructure

The deal brings isolated agent computers, persistent working context and networking into Baseten’s orbit. The companies say Blaxel’s current service will continue as integration begins.

By 2 min read
Baseten Acquires Blaxel to Add Agent Execution to Its AI Infrastructure
Baseten Acquires Blaxel to Add Agent Execution to Its AI Infrastructure

Listen to this story

The audio brief

About 1:30
0:001:30
Read transcript
Baseten is acquiring Blaxel, adding the infrastructure agents need to do work between model calls. The goal is a single platform where an agent can run code, preserve its working context, and connect to tools and outside systems alongside the models it uses. Financial terms were not disclosed. Blaxel brings three main pieces. Its Sandboxes are isolated micro-virtual machines where agents can write and execute code; Blaxel says they can suspend and resume in about 25 milliseconds. Agent Drive is a distributed filesystem that keeps versioned files, code, and working context available across sessions. And its networking layer connects agents to APIs, tools, Model Context Protocol servers, and other agents, with isolation and access controls. The strategic rationale is latency. An agent may repeatedly alternate between inference, code execution, storage, and external tools. Baseten and Blaxel argue that keeping those components close together could reduce the delay added by crossing network boundaries. But that is a technical rationale, not a published performance result from the combined platform. For Blaxel customers, there is no immediate change: access, credits, support contacts, and the existing team remain in place initially. Baseten says it will start with Sandbox products, without giving a timeline for broader integration. The first concrete test is whether those Sandboxes become a useful extension of Baseten’s training and inference services while Blaxel’s current platform continues operating.

Story brief

3 key points

Baseten is acquiring Blaxel to extend its model infrastructure into the execution layer agents need for multi-step work. Blaxel contributes isolated micro-VM Sandboxes, durable file storage through Agent Drive, and controlled connections to APIs, tools, MCP servers, and other agents. Customers will initially see no change, and financial terms, product timelines, and performance results remain undisclosed. The...

  1. 01

    Blaxel’s Sandboxes reportedly suspend and resume in about 25 milliseconds.

  2. 02

    Agent Drive preserves versioned files, code, and working context across sessions.

  3. 03

    Blaxel customers retain existing access, credits, support contacts, and team continuity initially.

Baseten has acquired Blaxel, bringing agent-execution infrastructure into its model training and inference business. The companies aim to build one platform where agents can run code, keep their working state and connect to outside systems alongside the models they call.

Financial terms were not disclosed. Baseten is buying more than a feature: Blaxel provides the computing environments, storage and network connections needed by agents that take actions over many steps rather than return a single model response.

The pieces an agent needs to keep working

A long-running agent may write code, use a tool, save files and pick up work in a later session. Blaxel built distinct infrastructure for each part of that process, with isolation intended to keep an agent’s computing environment separate from other workloads.

What Blaxel brings to Baseten

  • Sandboxes: isolated micro-virtual machines where agents can write and run code. Blaxel says they suspend and resume in about 25 milliseconds.
  • Agent Drive: a distributed filesystem for durable, versioned files, code and working context across sessions.
  • Networking: connections to tools, APIs, Model Context Protocol servers and other agents, with isolation and access controls.

Why distance is the technical issue

The companies’ rationale is that each trip across a network boundary can add delay when an agent repeatedly alternates between model calls and other work. They say colocating inference with compute, storage and networking can reduce that accumulating latency. That remains the companies’ technical argument for the combination, not a published result from the combined platform.

No immediate move for Blaxel customers

Blaxel says its platform will keep operating, while customer access, credits, support contacts and the existing team remain unchanged initially. Baseten plans to build products from Blaxel’s infrastructure primitives, starting with Sandboxes. The announcement gives no timetable for those products or for bringing the full storage and networking stack into Baseten’s platform.

That leaves the acquisition as a strategic commitment rather than a finished unified product. The first concrete test will be how Baseten turns Sandboxes into an offering that fits with its existing inference and training services while Blaxel continues to serve its current customers.

Sources

  1. baseten.coBlaxel is joining Baseten to build the future of agentic infrastructure
  2. blaxel.aiBlaxel is joining Baseten | Infrastructure for agents | Blaxel
  3. pulse2.comBaseten Acquires Blaxel To Build Integrated Agentic AI Infrastructure Platform

Loading discussion...