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. Lee 4 puntos de vista con sus evidencias y enlaces a las fuentes.

Amir Haghighat, Tuhin Srivastava, Paul Sinai
Leer los puntos claveAbrir Editor (se abre en una pestaña nueva)

De un vistazo

  • 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.

    Ver el momento de apoyo · Párrafo 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.

    Ver el momento de apoyo · Párrafo 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.

    Ver el momento de apoyo · Párrafo 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.

    Ver el momento de apoyo · Párrafo 16

Pasajes clave4

Pasajes atribuidos con contexto para verificarlos. Abra el texto original para comprobar la fuente.

Párrafo 16 (se abre en una pestaña nueva)
infrastructure design philosophy

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

Extracto 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·
Párrafo 6 (se abre en una pestaña nueva)
agent sandbox performance

MicroVM sandboxes with 25ms suspend/resume

Extracto 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·
Contexto

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.

Párrafo 10 (se abre en una pestaña nueva)
inference colocation for agents

Inference must sit adjacent to compute, storage, and network

Extracto 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·

Fuente y metodología

Estas perspectivas enlazan a sus fuentes originales. Las paráfrasis están identificadas y no son citas textuales.

Abrir transcripción o material de origen (se abre en una pestaña nueva)Reportar un problema