Sandbox isolation types
Sandbox providers keep code apart in four ways: microVMs, containers, user-space kernels and full VMs. 43 of the 79 providers listed here use microVMs.
Updated
- 43providers
MicroVM
Each sandbox has its own kernel inside a small virtual machine. Firecracker and Cloud Hypervisor are the common ones.
+37 more$0.008from, per vCPU-hour - 10providers$0.020from, per vCPU-hour
- 5providers
User-space kernel
A kernel written to run as a normal program handles the sandbox's system calls. gVisor is the common one.
$0.001from, per vCPU-hour - 19providers$0.005from, per vCPU-hour
How they compare
How each type keeps sandboxes apart
- Own kernel
- Example
- Firecracker
- Providers
- 43
- Own kernel
- No
- Example
- Docker, OCI
- Providers
- 10
- Own kernel
- In user space
- Example
- gVisor
- Providers
- 5
- Own kernel
- Example
- KVM
- Providers
- 19
Also browse by
Other ways to group the providers