Security model

OmniRun uses Firecracker microVMs for hardware-level isolation. Each sandbox runs its own Linux kernel, unlike containers which share the host kernel.

KVM hardware virtualizationGuest kernel per sandbox

Isolation stack

Layers from your code down to the host. The full security overview covers the controls and their limits.

Isolation stack

// Isolation layers (top → bottom)
'Your Code'        // Userspace
'Guest Kernel'     // Dedicated per sandbox
'microVM'  // Minimal VMM
'KVM'              // Hardware virtualization
'Host OS'          // Hardened host

Try it — Isolation Check

Benchmarks

Sandboxes are restored from a Firecracker snapshot, so a new sandbox is typically ready in under a second.

Sandbox create (snapshot restore)	Under 1 s, typical

Sandboxes resume from a Firecracker memory snapshot instead of cold-booting a kernel. Time from API call to a ready sandbox is typically under a second for the base templates; it varies with template size and host load. This is an operational observation, not a published benchmark: measure it for your own workload with the example below.

Try it — Benchmark