- Home
- Server Virtualization Software
- Firecracker
Firecracker
What it is
Firecracker is open-source virtualization technology for running container and function workloads in lightweight microVMs. It uses Linux KVM hardware virtualization to isolate workloads, and its five emulated devices are intended to reduce each microVM’s attack surface. The project states that microVMs start in under 125 ms and add under 5 MiB of memory overhead per VM. A host can create up to 150 microVMs per second and run thousands on one server. A RESTful API configures and starts microVMs, while built-in rate limiters govern network and storage use, including bandwidth and operations. The companion jailer applies Linux user-space security barriers as another defense layer. Firecracker supports Linux hosts and Linux guests with kernel versions 4.14 and above, as well as OSv guests. Listed production hardware includes 64-bit Intel, AMD, and Arm CPUs with hardware virtualization support. It supports VM snapshots but not GPU acceleration. The project is free under the Apache 2.0 license. Integrations include containerd, Kata Containers, E2B, Fly.io, Koyeb, Northflank, OpenNebula, Qovery, and microvm.nix. On aarch64, the pl031 RTC device does not support interrupts, so guest programs using an RTC alarm will not work.
For and against
For
- Free and open source under Apache 2.0.
- Uses KVM hardware virtualization to isolate workloads.
- RESTful API configures and starts microVMs.
- Built-in rate limiters govern network and storage use.
- VM snapshots are supported.
Against
- GPU acceleration is not supported.
- aarch64 RTC alarms do not work with the pl031 device.
- Requires hardware virtualization support.
The verdict
Firecracker provides Linux-based microVM virtualization with an API, resource controls, and a companion jailer. Note the stated aarch64 RTC alarm limitation and lack of GPU acceleration.
Who it suits
Firecracker suits developers and operators running container or function workloads on Linux hosts who need lightweight microVMs. It is relevant to teams using its listed integrations or self-hosted virtualization.
Plans and prices
Firecracker VMM
Open source · Apache 2.0 license
Read 7 Oct 2026 · firecracker-microvm.github.io
On the record
- Control API
- A RESTful API controls the Firecracker process, including microVM configuration and startup.firecracker-microvm.github.io · read 7 Oct 2026
- Density
- Firecracker says a host can create up to 150 microVMs per second and pack thousands onto one server.firecracker-microvm.github.io · read 7 Oct 2026
- GPU acceleration
- Nofirecracker-microvm.github.io · read 20 Sep 2026
- Guest architecture
- bothfirecracker-microvm.github.io · read 20 Sep 2026
- Host platforms
- Linuxfirecracker-microvm.github.io · read 20 Sep 2026
- Integrations
- The site lists integrations including containerd, Kata Containers, E2B, Fly.io, Koyeb, Northflank, OpenNebula, Qovery, and microvm.nix.firecracker-microvm.github.io · read 7 Oct 2026
- Isolation
- Firecracker uses Linux KVM hardware virtualization to isolate microVM workloads.firecracker-microvm.github.io · read 7 Oct 2026
- Jailer
- The companion jailer applies Linux user-space security barriers as a second line of defense if the virtualization barrier is compromised.firecracker-microvm.github.io · read 7 Oct 2026
- Minimal design
- Firecracker exposes five emulated devices and says this reduces the attack surface of each microVM.firecracker-microvm.github.io · read 7 Oct 2026
- Notable limitation
- On aarch64, the pl031 RTC device does not support interrupts, so guest programs using an RTC alarm will not work.github.com · read 7 Oct 2026
- Open source and license
- Firecracker is open source and licensed under Apache 2.0.firecracker-microvm.github.io · read 7 Oct 2026
- Operating systems
- Firecracker supports Linux host and guest operating systems with kernel versions 4.14 and above, as well as OSv guests.firecracker-microvm.github.io · read 7 Oct 2026
- Purpose
- Firecracker is open source virtualization technology for running secure, multi-tenant container and function workloads in lightweight microVMs.firecracker-microvm.github.io · read 7 Oct 2026
- Resource controls
- Built-in rate limiters control network and storage resource use, including bandwidth and operations.firecracker-microvm.github.io · read 7 Oct 2026
- VM snapshots
- Yesfirecracker-microvm.github.io · read 20 Sep 2026
- Startup and memory
- The site states that microVMs start in under 125 ms and have under 5 MiB of memory overhead per VM.firecracker-microvm.github.io · read 7 Oct 2026
- Support
- The project directs community questions to its Slack workspace and GitHub repository issues.github.com · read 7 Oct 2026
- Supported hardware
- The site lists 64-bit Intel, AMD, and Arm CPUs with hardware virtualization support as generally available for production workloads.firecracker-microvm.github.io · read 7 Oct 2026