flâneur

Let's discuss sandbox isolation

shayon.dev · 3,762 words · saved by 1 readers

A dive into the spectrum of sandboxing and isolation, from Linux namespaces and gVisor to hardware-enforced microVMs and WebAssembly, and why picking the right boundary matters for multi-tenant workloads.

There is a lot of energy right now around sandboxing untrusted code. AI agents generating and executing code, multi-tenant platforms running customer scripts, RL training pipelines evaluating model outputs—basically, you have code you did not write, and you need to run it without letting it compromise the host, other tenants, or itself in unexpected ways. The word "isolation" gets used loosely. A Docker container is "isolated." A microVM is "isolated." A WebAssembly module is "isolated." But these are fundamentally different things, with different boundaries, different attack surfaces, and dif

saved by

related reading