Skip to content

Build1 publisher3 min readPublished

Baseten buys Blaxel to put the agent sandbox on the same network side as the model call

Baseten's case for owning the agent runtime is that latency and idle compute accumulate at every boundary an agent crosses between the model call and its sandbox, on numbers Blaxel reported itself.

The Engineer · Build desk

Photograph accompanying Baseten buys Blaxel to put the agent sandbox on the same network side as the model call
Photo: baseten.co

What happened

  • Baseten said on September 10th that it is acquiring Blaxel, folding an agent execution business into an inference company that was valued at $13 billion in June.
  • Financial terms were not disclosed, and Baseten did not say whether the deal involved cash, stock or a combination of the two.
  • Blaxel gives each agent an isolated computer with persistent files through Agent Drive and a networking layer out to APIs, tools, Model Context Protocol servers and other agents.
  • Blaxel will keep operating and its existing product stays available while Baseten begins the integration.
  • Blaxel went through Y Combinator's Spring 2025 batch and raised a $7.3 million seed round led by First Round Capital in July.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • decision A team that pairs a serving vendor with a separate sandbox provider will find the co-location choice made upstream by whoever it buys from, so region placement turns into a procurement question.
  • exposure Putting the model endpoint and the agent's working files under one supplier means one availability domain and one invoice covering both halves of every step.
  • constraint Blaxel's scale figures were self-reported at the seed round, so a team evaluating the combined stack has no independent measurement of the runtime under load.

An agent step is several calls. The model returns something, code runs somewhere with a filesystem, a tool or an MCP server answers, then the agent waits. When the serving layer and the execution layer come from different vendors, each of those handoffs crosses the boundary between them. Blaxel's argument in its announcement thread is that inference has to sit beside compute, storage and networking because that latency compounds every time an agent crosses a network boundary [11]. Baseten, whose business is serving and training models [24], says the combination lets it optimize the model call, the execution environment, state and the network path as one system [22].

The figure under that argument is 25 milliseconds. Blaxel says its per-agent micro-virtual-machine sandboxes suspend and resume in roughly that time, preserving memory state and scaling down while idle [8]. It is a measurement of Blaxel's own environment. It transfers to your agent if the resume lands inside a step a user is already waiting through, and if the agent idles in blocks long enough that suspending is worth the bookkeeping. Where it pays is idle compute and network distance, which accumulate across a task as the agent executes code, reads files and contacts tools [21]. A sandbox placed far from the serving endpoint pays the boundary cost on every one of those steps [11].

Baseten was founded in 2019 by Tuhin Srivastava, Amir Haghighat, Phil Howes and Pankaj Gupta after they worked together at Gumroad [16], on the thesis that model serving would become the bottleneck as machine learning moved into customer-facing products [17]. Haghighat said people initially called the inference focus "stupid," because a model had to be trained before it could be served [18].

Blaxel's six founders came out of ForePaaS, the analytics platform OVHcloud acquired in 2022 [12][13]. Paul Sinai, Blaxel's co-founder and CEO, told VentureBeat in a July 17th, 2025 interview that conventional cloud providers were designed for the software-as-a-service era, while agents required their own type of infrastructure [19]. The seed round closed in July and the acquisition was announced on September 10th, about two months apart [23].

The near-term product is narrower than the rationale. Baseten says it will add products built on Blaxel's technology, beginning with its Sandboxes [5]. For a team running an agent across two vendors today, the question to put to that product is whether a sandbox and a serving endpoint can be pinned to the same region, and what the resume path costs when they cannot. Sinai's stated interest in the deal is having the model-serving layer inside the same organization as the sandboxes, storage and networking his six-founder team has built since 2024 [20].

What to watch

  • Whether Baseten's Sandboxes ships a documented way to pin a sandbox to the same region as the serving endpoint.
  • Whether Blaxel's standalone runtime gets a deprecation date once integration is under way.
  • Whether the consideration, cash or stock, surfaces in any later disclosure.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories