nafyi.

Blaxel is joining Baseten to build the future of agentic infrastructure

Baseten Blog ·

A source describing Blaxel's technical infrastructure for autonomous agents—covering microVM sandbox performance, production networking design, inference colocation requirements, and foundational infrastructure design principles—based on statements attributed to Blaxel. Lisez 4 points de vue avec leurs éléments à l’appui et les liens vers les sources.

Amir Haghighat, Tuhin Srivastava, Paul Sinai
Lire les points clésOuvrir Éditeur (s’ouvre dans un nouvel onglet)

En un coup d’œil

  • MicroVM sandboxes with 25ms suspend/resume

    Blaxel built isolated microVM sandboxes for agents, enabling safe code execution and state persistence. They suspend and resume in 25 milliseconds—up to 5× faster than other sandbox products—and can remain idle for months at near-zero cost while retaining state.

    Lire le moment probant · Paragraphe 6

  • Rebuilt networking layer with isolation and access controls

    Blaxel rebuilt its networking layer to connect agents with tools, MCP servers, APIs, and other agents—designed specifically to meet production teams’ requirements for isolation and access controls.

    Lire le moment probant · Paragraphe 9

  • Inference must sit adjacent to compute, storage, and network

    The Blaxel team observed that inference for autonomous agents is no longer a remote service call: it must be colocated with compute, storage, and networking to avoid compounding latency on every agent loop.

    Lire le moment probant · Paragraphe 10

  • First-class consideration of performance, reliability, security, and ownership

    Both Blaxel and Baseten built their infrastructure from the ground up—prioritizing performance, reliability, security, scalability, flexibility, cost-efficiency, and customer visibility, control, and ownership—rather than taking the fastest path to market.

    Lire le moment probant · Paragraphe 16

Passages clés4

Passages attribués et accompagnés du contexte nécessaire à leur vérification. Ouvrez le texte original pour vérifier la source.

Paragraphe 16 (s’ouvre dans un nouvel onglet)
infrastructure design philosophy

First-class consideration of performance, reliability, security, and ownership

Extrait original

Both companies built from the ground up for what it would take to truly scale the workload to our customers’ requirements, rather than taking the fastest path to market. We had both decided that performance, reliability, scalability, security, flexibility, and cost-efficiency needed to be first-class considerations. And we each believed customers need maximum visibility, control, and ownership.
Amir Haghighat, Tuhin Srivastava, Paul Sinai·
Paragraphe 6 (s’ouvre dans un nouvel onglet)
agent sandbox performance

MicroVM sandboxes with 25ms suspend/resume

Extrait original

Every agent gets its own microVM. We made them extremely fast: suspend and resume in 25 milliseconds, up to 5x faster than other sandbox products. A sandbox can sit idle for months at close to zero cost and come back before the model finishes its next sentence, so state persists without paying for compute you aren't using.
Amir Haghighat, Tuhin Srivastava, Paul Sinai·
Contexte

Sandboxes came first because nothing else works without them. Agents write and run code, call tools, and carry state across long tasks, and you can't do that safely in a shared process.

Paragraphe 10 (s’ouvre dans un nouvel onglet)
inference colocation for agents

Inference must sit adjacent to compute, storage, and network

Extrait original

The primitive we didn't own was inference. We've seen open-weight & custom models become core to how autonomous agents get deployed in production. Inference is no longer a service you call from another data center. It has to sit next to compute, storage, and network; or latency compounds on every loop.
Amir Haghighat, Tuhin Srivastava, Paul Sinai·
Paragraphe 9 (s’ouvre dans un nouvel onglet)
production networking for agents

Rebuilt networking layer with isolation and access controls

Extrait original

And agents have to talk to things. Tools, MCP servers, APIs, other agents. We rebuilt a networking layer that connects all of these pieces with the isolation and access controls a production team will actually sign off on.
Amir Haghighat, Tuhin Srivastava, Paul Sinai·

Source et méthodologie

Ces points de vue renvoient à leurs sources originales. Les reformulations sont signalées et ne sont pas des citations mot à mot.

Ouvrir la transcription ou les documents sources (s’ouvre dans un nouvel onglet)Signaler un problème