Key Takeaways
- The company migrated hundreds of millions of projects to a microVM-based sandbox engine without reported disruption or data loss.
- The architecture combines hardware virtualization, minimal guest kernels, host-side controls, and container-level restrictions.
- Warm pools and remote block storage provide stronger isolation while handing off sandboxes in roughly 500 milliseconds.
AI agents are moving beyond chat windows. They write and execute code, install packages, query internal systems, and interact with cloud services. That expanded reach gives infrastructure teams a harder problem: how to let agents perform useful work without treating generated code as trusted.
Replit addresses this with a new sandbox architecture built around lightweight virtual machines. Announced on November 4, 2026, the production rollout replaces a runtime that relied primarily on Docker containers spread across Google Compute Engine VMs. The company migrated hundreds of millions of projects without data loss while preserving the speed expected from an interactive development environment.
The project began in November 2025, with internal use starting by February. The engineering team then spent several months hardening and deploying the system. The timing reflects a broader focus on agent containment. The National Institute of Standards and Technology has put AI risk management and agent standards on its agenda, while incidents involving OpenAI and Anthropic have illustrated how autonomous systems can reach resources outside their intended scope.
While containers remain useful, they share the host kernel. A reachable kernel vulnerability can therefore make a container escape considerably more consequential. The microVM design gives each sandbox its own Linux kernel, with KVM providing a hardware-assisted boundary between customer workloads and the host.
Containers have not disappeared. Minimal runc containers still separate processes and supporting services inside each microVM. The architecture applies namespaces, seccomp restrictions, device controls, resource limits, and role-specific capabilities within the guest. The virtual machine monitor, meanwhile, runs under an unprivileged identity without Linux capabilities.
Cloud Hypervisor was selected as the virtual machine monitor. Features including device hotplug, memory snapshots, virtiofs, and live migration helped support warm pools and on-demand disk attachment. A minimal init process manages containers inside the guest, while gRPC over vsock provides host-to-guest communication without requiring an IP network.
Reducing the guest kernel minimized the attack surface. The configuration starts with tinyconfig and excludes hardware support that a cloud coding environment is unlikely to use, including Bluetooth, wireless, USB, and display drivers. Required drivers are built in, and module loading is disabled during initialization.
According to published company data based on records from CVEProject and kernel.org, an internal audit reviewed 6,211 Linux-CNA CVEs published between June 1 and November 4, 2026. The team reported 5,969, or 96.1%, were addressed through incorporated upstream fixes or exclusion of affected code. Configuration excluded 676 CVEs, while 4,375 fixes landed before disclosure.
Isolation also extends beyond compute. Host-side proxies enforce egress rules, filter DNS, and inspect TLS handshake hostnames without decrypting application payloads. Credential brokers attach authorization for services such as GitHub and Google Docs without exposing account API keys to workloads. npm and pip traffic passes through a registry firewall intended to block known malicious packages.
To prevent storage constraints from undermining startup speed, remote block storage fetches filesystem data on demand, and copy-on-write disks make workspace forks inexpensive. A vhost-user virtio-blk backend presents those remote disks to the guest as ordinary virtual block devices.
Warm pools complete the performance profile. The organization reported that acquiring a sandbox takes roughly 500 milliseconds, including mounting customer volumes and configuring supporting services in parallel. Orchestrating tens of thousands of those environments is a separate challenge, one also being explored through projects such as the Kubernetes Agent Sandbox.
Agent infrastructure is evolving into a distinct security and operations layer. Replit offers Bring Your Own Cloud support across AWS, Google Cloud, and Azure to add portability, but the more consequential shift is architectural. Agent code is being treated as potentially hostile from the moment it runs, with isolation, credentials, networking, monitoring, and storage designed around that assumption.
⬇️