CreateOS Sandbox

What CreateOS Sandbox does

CreateOS Sandbox provides isolated execution environments for AI agents using Firecracker micro-VMs. The underlying sandbox model gives each environment its own kernel, separating agent workloads from a shared execution context. This makes the product relevant to agents that need to run code inside dedicated micro-virtual machines.

The platform also includes private networking and a pause-to-zero capability. These are part of the sandbox environment rather than separate tools: private networking defines the network model available to workloads, while pause-to-zero describes the platform's ability to pause a sandbox down to zero.

How it works

An AI agent uses CreateOS Sandbox to work with Firecracker-based micro-VM sandboxes. The micro-VM approach supplies the execution boundary, and the own-kernel design is a defining part of that boundary. Sandboxes can use private networking, giving the environment a network configuration intended to remain private.

The product can be reached through several interfaces. Applications can use the SDK, command-line workflows can use the CLI, MCP-compatible agent workflows can use the MCP interface, and HTTP-based applications can use the REST interface. The appropriate entry point depends on how the calling application is built.

Tools and capabilities

• Firecracker micro-VM sandboxes for AI agents
• A separate kernel for each sandbox environment
• Private networking
• Pause-to-zero capability
• SDK access for application integration
• CLI access for command-line workflows
• MCP access for agent tool usage
• REST access for HTTP clients

The MCP interface is the relevant option when an AI agent needs to interact with CreateOS Sandbox through Model Context Protocol. The SDK, CLI, and REST interfaces provide alternatives for applications or workflows that do not use MCP.

Limitations and notes

CreateOS Sandbox is focused on sandboxed execution through Firecracker micro-VMs. Its listed access surfaces are the SDK, CLI, MCP, and REST interfaces, so teams should select an interface based on their agent or application architecture. The defining environment characteristics are the dedicated kernel, private networking, and pause-to-zero behavior.