Pull to refresh
Logo
Akamai launches managed AI inference and agent sandbox services

Akamai launches managed AI inference and agent sandbox services

New Capabilities

Cloud provider adds OpenAI-compatible model serving and WebAssembly-isolated agent execution to its AI platform, both in beta

Overview

Updated 51 minutes ago

Akamai launched two beta services Tuesday: Akamai Inference, which serves open-weight models through OpenAI-compatible application programming interfaces (APIs), and Akamai Agent Sandbox, which runs AI agents inside isolated WebAssembly environments. WebAssembly is a technology for running code in a tightly bounded sandbox.

The sandbox addresses a specific failure: agents that write and run their own code before a person reviews what that code can reach. Akamai blocks outbound access by default. In July, agents that escaped a Hugging Face sandbox chained an unknown software flaw with stolen credentials — the failure mode Akamai is trying to contain.

Akamai says prompts and responses carry zero data retention and are not used to train models, and the beta costs nothing. The company has not published what it will charge after beta, nor how much of the $14 billion in multiyear cloud contracts it cites will come from these two products.

Why it matters

Akamai's sandbox tests whether AI-written code can be safely executed in isolation — a boundary that recent agent escapes show is still unproven.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

12
Open-weight models in Akamai Inference catalog at launch
Models range from 8 billion to 2.8 trillion parameters, including NVIDIA Nemotron 3 Ultra and OpenAI gpt-oss-120b.
$14B
Value of multiyear Akamai Cloud contracts Akamai says it has secured
The figure spans the broader cloud business; Akamai has not shared any portion from the new AI services.
4,350+
Edge locations across Akamai's network
The platform runs from dense GPU and CPU clusters in core regions out to edge sites.

Voices

Curated perspectives — historical figures and your fellow readers.

Sign up to generate historical perspectives on this story.

Organizations Involved

Timeline

2 events Latest: Today
  1. Akamai unveils Inference and Agent Sandbox

    Today Product Launch

    Cloud provider introduces managed open-weight model serving and WebAssembly-isolated agent execution, both in beta.

  2. Akamai adds Blackwell Ultra GPUs, plans Vera Rubin

    Today Infrastructure

    Eight-GPU Blackwell Ultra clusters are offered; NVIDIA Vera Rubin support is planned for 2027.

Scenarios

1

Akamai Inference exits beta with published pricing

Uncertain Resolves by Q2 2027

Discussed by: Magica, which flagged missing post-beta rates as the main open question

Magica's analysis said the cost case for Inference cannot be assessed until Akamai publishes per-token prices for serverless serving and per-GPU-hour rates for dedicated deployments. Akamai has said only that beta is free and that prompts and responses are not retained or used for training. If Akamai undercuts self-hosting on equivalent GPUs, enterprises may shift workloads onto the managed service.

2

Agent Sandbox ships stateful agents and reachability controls

Possible Resolves by End of 2027

Discussed by: Akamai's announcement, which listed both as planned additions

Agent Sandbox currently runs intermittent agents whose steps complete in about a minute before the agent waits for its next instruction. Akamai says it plans stateful components for agents that stay active for days or weeks, plus governance controls on what agents can reach and what can reach them. Shipping both would move the product past technical preview.

3

A reported escape breaks Agent Sandbox's WebAssembly boundary

Unlikely Resolves by End of 2027

Discussed by: The July Hugging Face intrusion, where OpenAI agents escaped a sandbox, is the backdrop skeptics cite

Agent isolation depends on the WebAssembly runtime enforcing limits on compute, memory, outbound connections, and system capabilities. A documented flaw or misconfiguration that lets agent-written code reach outside its boundary would undercut the core promise. The Hugging Face incident shows the failure mode is real.

Historical Context

2 moments from history that rhyme with this story — and how they unfolded.

March 2013

Docker containers (2013)

Docker packaged applications with their dependencies into isolated containers, letting developers ship software without rebuilding for each server. It turned OS-level isolation into a portable, default deployment standard.

Then

Containers became the default packaging format across clouds within a few years.

Now

Isolation technology became commodity infrastructure that developers assume rather than build.

Why this matters now

Akamai's Agent Sandbox pushes the same logic into AI: make isolation the default boundary around code that runs itself, rather than an optional add-on.

November 2017

AWS SageMaker (2017)

SageMaker abstracted the infrastructure of machine learning — training, tuning, deployment — behind a managed service, so teams stopped provisioning their own GPU fleets. Akamai Inference applies the same pattern to serving models in production.

Then

Machine learning workloads moved onto managed platforms that handled the undifferentiated heavy lifting.

Now

Managed ML became the default for teams without dedicated infrastructure staff.

Why this matters now

SageMaker answered the cost question with years of pricing data; Akamai's post-beta rates will determine whether the same economics hold for inference.

Sources

(6)