What everyone gets wrong about building sandboxes

Inngest has launched Sandboxes as durable, isolated compute environments integrated directly into its agent orchestration platform, allowing agents to clone repositories, execute code and tests, and manage sub-agents without relying on separate infrastructure vendors. The company designed the system around rapid startup times, full VM capabilities including VPC networking and SSH, and a simple developer experience, using cloud-hypervisor rather than Kubernetes or Firecracker because it supports CPU, memory, network, and device hotplugging, virtio-fs, and snapshots. Its architecture uses generic prewarmed pools of snapshotted virtual machines that are assigned to customers only when needed, then resized, connected to the appropriate VPC, and mounted with workload files, avoiding separate pools for each customer, image, network, or machine size. A custom control plane, eBPF-based networking stack with VXLAN tenant isolation, and ZFS snapshots support high-throughput provisioning and consistent machine-state capture. Inngest plans to extend this foundation to durable sandboxes that can be rewound or forked at individual command steps, as well as serverless functions, managed containers, and long-running VMs, with opt-in VPC networking expected to follow.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.