GravityKit
GravityKit ships weekly across a whole plugin suite, with an MCP server now part of the lineup.
Comparison · Infra & APIs
Firecracker vs Incus
A side-by-side editorial comparison of Firecracker and Incus — release velocity, themes, recent moves, and the top alternatives to consider.
Firecracker vs Incus: at a glance
What is Firecracker?
Firecracker's microVMs can now grow and shrink devices while running.
1.16.0 in June added developer-preview hotplug and hot-unplug for PCI virtio block, pmem and net devices on a live microVM, with the guest responsible for rescanning the bus and removing the device first since no notification mechanism exists yet. The same release added vsock Unix socket path overriding on snapshot restore, rate limiting for serial console output with a dropped-bytes metric, and per-callsite log rate limiting. 1.16.1 followed with a vsock fix for connections timing out after restore when a snapshot caught an in-flight TX descriptor. Earlier in the window, 1.15.0 added the VMClock device and Intel Granite Rapids support, and the April patches hardened the PCI transport against CVE-2026-5747.
What is Incus?
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
Firecracker vs Incus: editorial side-by-side
Firecracker
0.0INFRA · APIS
Firecracker's microVMs can now grow and shrink devices while running.
◆ Current state
1.16.0 in June added developer-preview hotplug and hot-unplug for PCI virtio block, pmem and net devices on a live microVM, with the guest responsible for rescanning the bus and removing the device first since no notification mechanism exists yet. The same release added vsock Unix socket path overriding on snapshot restore, rate limiting for serial console output with a dropped-bytes metric, and per-callsite log rate limiting. 1.16.1 followed with a vsock fix for connections timing out after restore when a snapshot caught an in-flight TX descriptor. Earlier in the window, 1.15.0 added the VMClock device and Intel Granite Rapids support, and the April patches hardened the PCI transport against CVE-2026-5747.
◆ Where it's heading
The through-line is snapshots and the PCI transport maturing together. Firecracker's value has always been fast boot from a snapshot, and the recent fixes are all in the seams that opens up — TX descriptors in flight when a snapshot is taken, vsock paths that change on restore, virtio device state machines that must be validated the same way on PCI as on MMIO. Hotplug extends the same idea from restore-time to run-time: a microVM that can change shape is one you can keep rather than replace.
◆ Prediction
Hotplug shipped explicitly as a developer preview requiring manual guest bus rescans, so the stated gap is an automatic notification mechanism. That is the obvious next step before the feature leaves preview.
Incus
5.0INFRA · APIS
Incus settled its 7.0 LTS, then went straight back to a monthly feature cadence.
◆ Current state
7.0.0 LTS landed in early May and became the supported baseline, followed by 7.0.1 as its first patch. The feature branch has not paused: 7.1 in May cleaned up the issues the LTS surfaced, 7.2 in June added migration-compatible hypervisor flags for stateful migration and aligned node-specific network configuration, and 7.3 at the end of July added native Windows and macOS installers to the build workflow, a QMP command timeout, and /32 and /128 addresses for OCI containers. Underneath, QEMU capabilities like SPICE, 9p and virtio audio are increasingly gated on runtime detection rather than assumed.
◆ Where it's heading
The rhythm is a monthly feature release running alongside a long-term branch, and the recent work leans toward reach rather than new primitives: clients built natively for Windows and macOS, translations updated in nearly every release, feature gating so the same daemon behaves correctly across host configurations. Stateful migration getting migration-compatible CPU flags is the most operationally significant item, since it is what makes live migration work across non-identical hosts.
◆ Prediction
The cadence in this window is a feature release roughly every four to six weeks with LTS patches interleaved, so a 7.4 is the expected next step. The entries give no indication of a headline feature queued for it.
Alternatives to Firecracker and Incus
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Firecracker or Incus.
LibreSpeed
After a two-year redesign, LibreSpeed is adding tests instead of polishing pixels.
Nautobot
A security advisory cycle forced Nautobot to break its REST API on both supported branches at once.
Gatekeeper
Gatekeeper grew a package manager for policies — and a benchmark to prove they are not too slow.
GoCD
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
runc
runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.
See all Firecracker alternatives → · See all Incus alternatives →
Recent activity from Firecracker and Incus
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7d agoIncusNative Windows and macOS installers; QMP command timeouts
- 27d agoIncusFirst patch release on the 7.0 LTS branch
- 1mo agoFirecrackerVsock timeout after snapshot restore, and jailer symlink revert
- 1mo agoIncusMigration-compatible hypervisor flags for stateful migration
- 2mo agoFirecrackerFirecracker v1.16.0 ⚡
- 2mo agoIncusFixes for issues surfaced by the 7.0 release
- 3mo agoIncusIncus 7.0 LTS, with runtime-detected QEMU feature gating
- 4mo agoFirecrackervirtio-rng entropy cap and PCI transport hardening (CVE-2026-5747)
- 4mo agoFirecrackerCVE-2026-5747 hardening on the 1.15 branch
- 4mo agoIncusVolume snapshots while attached; OVN dhcp gateway option
- 4mo agoFirecrackerTCP SYN options length validation with MMDS enabled
- 5mo agoFirecrackerVMClock device and Intel Granite Rapids support
Frequently asked questions
What is the difference between Firecracker and Incus?
They serve adjacent needs but don't currently overlap on shipped themes. Incus is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Firecracker better than Incus?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Incus is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Firecracker?
Top Firecracker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Firecracker alternatives" section above for the current picks, or visit /alternatives/firecracker for the full list with editorial commentary on each.
What are the best alternatives to Incus?
Top Incus alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Incus alternatives" section above for the current picks, or visit /alternatives/incus for the full list with editorial commentary on each.