Firecracker
firecracker-microvm.github.io
- Free plan
- Linux
- API
- Self-hosted
What Firecracker is
Firecracker is open-source virtualization software for running container and function workloads in lightweight microVMs. It uses Linux KVM hardware virtualization to isolate workloads and exposes five emulated devices, a design intended to reduce each microVM’s attack surface. Firecracker states that microVMs start in under 125 ms, add under 5 MiB of memory overhead, and can be created at a rate of up to 150 per second on a host. Thousands can run on one server. A REST API configures and starts microVMs, while built-in rate limiters manage network and storage resources. The companion jailer adds Linux user-space security barriers. Linux hosts and guests with kernel versions 4.14 and above are supported, along with OSv guests. VM snapshots are available, but GPU acceleration is not. Firecracker is free under Apache 2.0 and lists integrations such as containerd, Kata Containers, Fly.io and OpenNebula.
Who it suits
It suits teams running isolated, high-density container or function workloads on Linux infrastructure. Its API, jailer and resource controls also fit self-hosted virtualization deployments.
Good to know, and what to watch
- Free and open source under Apache 2.0
- Starts microVMs in under 125 ms
- Under 5 MiB memory overhead per VM
- REST API controls configuration and startup
- Supports VM snapshots and multiple CPU architectures
- No GPU acceleration
- aarch64 RTC alarms do not work
- Requires Linux hosts with KVM support
Plans
Every plan and priceFirecracker VMM
Free plan
The verdict
Firecracker focuses on lightweight, isolated microVM workloads with a small device footprint and strong automation controls. Its Linux and KVM requirements, plus the aarch64 RTC limitation, should be checked before deployment.
What the maker publishes
- Control API
- A RESTful API controls the Firecracker process, including microVM configuration and startup. source
- Density
- Firecracker says a host can create up to 150 microVMs per second and pack thousands onto one server. source
- Free plan
- Yes source
- GPU acceleration
- No source
- Guest architecture
- both source
- Host platforms
- Linux source
- Integrations
- The site lists integrations including containerd, Kata Containers, E2B, Fly.io, Koyeb, Northflank, OpenNebula, Qovery, and microvm.nix. source
- Isolation
- Firecracker uses Linux KVM hardware virtualization to isolate microVM workloads. source
- Jailer
- The companion jailer applies Linux user-space security barriers as a second line of defense if the virtualization barrier is compromised. source
- Minimal design
- Firecracker exposes five emulated devices and says this reduces the attack surface of each microVM. source
- Notable limitation
- On aarch64, the pl031 RTC device does not support interrupts, so guest programs using an RTC alarm will not work. source
- Open source and license
- Firecracker is open source and licensed under Apache 2.0. source
- Operating systems
- Firecracker supports Linux host and guest operating systems with kernel versions 4.14 and above, as well as OSv guests. source
- Purpose
- Firecracker is open source virtualization technology for running secure, multi-tenant container and function workloads in lightweight microVMs. source
- Resource controls
- Built-in rate limiters control network and storage resource use, including bandwidth and operations. source
- VM snapshots
- Yes source
- Startup and memory
- The site states that microVMs start in under 125 ms and have under 5 MiB of memory overhead per VM. source
- Support
- The project directs community questions to its Slack workspace and GitHub repository issues. source
- Supported hardware
- The site lists 64-bit Intel, AMD, and Arm CPUs with hardware virtualization support as generally available for production workloads. source
Checked against the maker's pages on 7 Oct 2026.