SPACE

Overview

SPACE (Sandboxed Platform for Agentic Code Execution) is a sandbox platform for running code in isolated Firecracker microVMs. Applications use its HTTP API to create Linux environments, execute commands, collect output, and manage sandbox lifecycles. A template supplies the starting environment, and a sandbox is an instance of that environment with its own VM and writable filesystem.

Key Features

• Runs agent, user, and code-running jobs in isolated Firecracker microVMs.
• Exposes an HTTP API for creating Linux environments, executing commands, collecting output, and managing sandbox lifecycles.
• Supports multiple commands in the same sandbox, each with its own VM and writable filesystem.
• Uses templates to supply starting environments and sandboxes as instances of those environments.
• Provides asynchronous lifecycle operations through operation IDs that can be polled for completion.
• Streams command output over a separate data-plane connection using a session-scoped attachment token.

Use Cases

• Running an agent in a separate execution environment.
• Providing a user workspace for code execution.
• Executing code-running jobs in isolation.

Getting Started

• Follow Installation and configuration to deploy SPACE in a local Kind cluster and authenticate.
• Follow Your first sandbox to run a command and collect its output.

Deployment & Requirements

• The setup guide covers Kubernetes; the architecture guide also explains how SPACE can run without it.
• Host prerequisites, local Kind deployment, configuration defaults, authentication, verification, and teardown are covered in the installation documentation.
• A local deployment uses a Kind cluster and requires authentication.

Before You Adopt

• License: Apache-2.0. Review its terms before using, modifying, or distributing the project.
• Some API schema fields are marked incubating and are outside the supported contract.
• Sandbox lifecycle changes are asynchronous; clients poll an operation ID for completion.
• Command output uses a separate data-plane connection and a session-scoped attachment token.
• The documented setup path uses Kubernetes.