CreateOS Sandbox Explained: Hardware-Isolated Micro-VMs for AI Agents

If you run AI agents, CI pipelines, or user-submitted code in production, you need a sandbox that does not force you to choose between isolation and network access. Most options give you shared-kernel containers with a proxy bolted on. One escape, and everything is compromised. CreateOS Sandbox is different. Every workload runs in its own Firecracker micro-VM with a dedicated guest kernel. Egress is enforced in kernel via eBPF from outside the sandbox. Code running inside cannot route around policy, even if fully compromised. In this video, we cover: What CreateOS Sandbox is and why it exists Hardware isolation vs shared-kernel containers eBPF-based egress control with allowlists Fork — snapshot and clone a running sandbox in milliseconds Overlay networks, VPN, public ingress, S3 disks, and custom images Self-host the control plane in your own VPC Stripe CLI integration 51 runnable examples including Claude Managed Agent, multi-node clusters, batch inference, and more Get started: Web UI: CreateOS - Unified Workspace to Build, Deploy & Scale Applications CLI: createos sandbox create Docs: Quickstart | NodeOps SDK + Examples: GitHub - NodeOps-app/createos-sandbox-sdk · GitHub Claude Plugin: GitHub - NodeOps-app/createos-claude-plugins · GitHub 500 free credits, no card required.