Microsandbox provides a secure runtime for running untrusted code in lightweight microVMs, each with its own kernel, ensuring hardware-level isolation. It supports multiple languages and interfaces, allowing developers to run generated code, third-party software, or their own apps locally, in the cloud, or on their own infrastructure. The platform offers a single SDK and API, making the choice between local and cloud deployment a simple configuration change.
Funding
Funding not disclosed
Founders
Product
Problem
Traditional container runtimes like Docker share the host kernel, which creates a security risk when running untrusted code, such as AI-generated scripts or third-party applications. A compromise in one container can potentially affect the host system, making it unsafe to run unverified code in shared environments.
Solution
Microsandbox addresses this by providing a runtime that runs each sandbox as a microVM with its own dedicated kernel, creating a hardware-level boundary between the sandbox and the host. This approach allows developers to safely execute untrusted code, including generated code and third-party software, without the risk of a full system compromise. The platform supports a standard OCI-image workflow, making it a drop-in replacement for Docker for untrusted workloads. It offers a single SDK and API, so moving from local development to cloud deployment is a simple configuration change, not a rewrite. The runtime is open-source and Apache 2.0 licensed, allowing teams to inspect the security model and reproduce benchmarks. It can be run locally, in the Microsandbox cloud, or on a customer's own infrastructure via a bring-your-own-cloud option.
Target Audience
Primary customers are development teams and enterprises that need to run untrusted code, such as AI-generated scripts, third-party applications, or multi-tenant workloads, in a secure and isolated environment.
Features
- Each sandbox runs as a microVM with its own kernel, providing hardware-level isolation from the host system.
- Supports a standard OCI-image workflow, enabling easy migration from Docker for untrusted workloads.
- Includes a single SDK and API for Rust, TypeScript/Node, Python, Go, and a CLI, with MCP workflow support.
- Offers a "bring your own cloud" (BYOC) option for deploying the runtime on a customer's own infrastructure.
- Provides granular network egress controls, including default blocking of private, host-local, and metadata destinations, with options for allowlists or disabling egress entirely.
- Features destination-bound credentials, where real secrets are substituted host-side only for approved destinations, preventing credential leakage to untrusted sandboxes.