Akamai opens inference and agent-code sandbox betas on its cloud

Akamai has [introduced beta versions of Akamai Inference and Akamai Agent Sandbox](https://www.akamai.com/newsroom/press‑release/akamai‑launches‑ai‑inference‑service‑and‑agent‑execution‑environment). One serves model requests; the other provides an execution environment for the code an AI agent produces. Together they address two separate requirements for a team building an agent‑based application: obtaining model output and deciding where generated code may run. The availability statement is specific. Akamai Inference’s beta includes serverless deployment options, and Agent Sandbox is available in beta through the Spin SDK. Those stages matter when assessing the announcement: the company is describing new services that teams can evaluate, rather than establishing that every deployment option is generally available.

For inference, Akamai [describes managed access to open‑weight and custom models](https://www.akamai.com/newsroom/press‑release/akamai‑launches‑ai‑inference‑service‑and‑agent‑execution‑environment) through OpenAI‑compatible APIs. The service handles model execution, orchestration and authentication, with connections to data services in Akamai Cloud. The announcement discusses serverless, pay‑per‑use serving alongside dedicated deployments. Its beta availability statement specifically identifies the serverless option. A team planning a deployment still needs to check the models, configuration and service limits available to it. An OpenAI‑compatible interface describes the API approach; it does not establish that every application, model feature or existing integration can transfer without changes. The useful distinction is who operates the model‑serving layer. A managed endpoint lets the application send a request without the team also taking responsibility for the complete serving stack. The release does not publish a complete price list or a versioned compatibility matrix.

Agent Sandbox addresses the execution step after an agent has produced code. Akamai [says agents run on Akamai Functions](https://www.akamai.com/newsroom/press‑release/akamai‑launches‑ai‑inference‑service‑and‑agent‑execution‑environment), while the code they write runs in a separate, isolated environment. It describes WebAssembly isolation as the mechanism for limiting compute, memory, outbound connections and system capabilities. That architecture gives developers a different question to answer from model selection: which resources should the generated code be able to use? The application’s agent runtime and the code execution environment have different roles in that decision. Akamai’s description explains the intended boundary; it is not an independent security test or a guarantee that every program is safe to execute.

The [announcement](https://www.akamai.com/newsroom/press‑release/akamai‑launches‑ai‑inference‑service‑and‑agent‑execution‑environment) also says Akamai plans further capabilities governing what agents can reach and what can reach them. Those planned controls should be kept separate from the beta features described as available today. For a team evaluating the services, the immediate checks are therefore practical: whether the required model is available through the inference beta, whether the API supports the application’s requests, and whether the sandbox’s execution limits match the code it is expected to run. The company has supplied a model‑serving path and a generated‑code execution path under beta availability. Their suitability for a particular application still depends on the supported configuration and the team’s own evaluation. *Upper‑façade detail of Akamai’s Cambridge headquarters in a June 19, 2009 photograph. Historical company context, not the beta services or current infrastructure. Photo: [Coolcaesar](https://en.wikipedia.org/wiki/User:Coolcaesar) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Akamaiheadquarters.jpg), [CC BY‑SA 3.0](https://creativecommons.org/licenses/by‑sa/3.0/). Cropped and resized; image adaptations retain the same licence.*