← Back to home
Comparison · Infra & APIs

runc vs Skipper

A side-by-side editorial comparison of runc and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

runc vs Skipper: at a glance

FeatureruncSkipper
SectorInfra & APIsInfra & APIs
Velocity score2.56.3
Sparks · 30d00
Top themescontainer runtime, support policy, cve coordination, multi-branchapi-gateway, http-proxy, rfc9421, performance
Last editorial update1mo ago2h ago
WebsiteVisit →Visit →

What is runc?

runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.

1.5.0 in June was the first stable release of the 1.5.z series and the third under runc's formal release and support policy: 1.2.z and earlier are unsupported, 1.3.z receives only high-severity CVE fixes until the end of October 2026, and 1.4.z is limited to security and significant bugfixes. A month later 1.5.1 fixed a real-world regression — the maskPaths optimisation from 1.5.0-rc.3 broke tmpfs mounts with nr_inodes=1 on Ubuntu 20.04 kernels. In mid-June, CVE-2026-41579 was fixed simultaneously across 1.3.6, 1.4.3 and 1.5.0-rc.3 and released with no embargo.

Read the full runc trajectory →

What is Skipper?

Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement

Skipper v0.27 is shipping at a steady maintenance cadence with two functional additions of note: v0.27.96 adds native RFC 9421 HTTP Message Signatures filter support — a 2023 IETF standard for request signing gaining traction in financial services and regulated APIs. v0.27.95 delivers a shared parse cache across RouteGroups, producing a measured 21% load time reduction, 12% lower memory, and 26% fewer allocations on a 200-RouteGroup benchmark.

Read the full Skipper trajectory →

runc vs Skipper: editorial side-by-side

R
runc
INFRA · APIS
2.5

runc now publishes an end-of-life calendar, and three branches shipped the same CVE fix in two days.

◆ Current state

1.5.0 in June was the first stable release of the 1.5.z series and the third under runc's formal release and support policy: 1.2.z and earlier are unsupported, 1.3.z receives only high-severity CVE fixes until the end of October 2026, and 1.4.z is limited to security and significant bugfixes. A month later 1.5.1 fixed a real-world regression — the maskPaths optimisation from 1.5.0-rc.3 broke tmpfs mounts with nr_inodes=1 on Ubuntu 20.04 kernels. In mid-June, CVE-2026-41579 was fixed simultaneously across 1.3.6, 1.4.3 and 1.5.0-rc.3 and released with no embargo.

◆ Where it's heading

The project is behaving like infrastructure with a contract. Publishing dated support windows and shipping a coordinated fix across every live branch on the same day is the operating posture of a component that sits under every container on a host, where operators need to know what they are still entitled to. The CVE itself is instructive: a /dev symlink escape in the same family as three earlier CVEs, found by re-auditing the rootfs preparation code that had been hardened before.

◆ Prediction

1.5.0's notes state that a 1.6.0 is expected in late October 2026, which is also when 1.3.z support ends — so the next milestone is that pairing. Expect 1.5.z patches until then.

S
Skipper
INFRA · APIS
6.3

Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement

◆ Current state

Skipper v0.27 is shipping at a steady maintenance cadence with two functional additions of note: v0.27.96 adds native RFC 9421 HTTP Message Signatures filter support — a 2023 IETF standard for request signing gaining traction in financial services and regulated APIs. v0.27.95 delivers a shared parse cache across RouteGroups, producing a measured 21% load time reduction, 12% lower memory, and 26% fewer allocations on a 200-RouteGroup benchmark.

◆ Where it's heading

Skipper is building out its security posture at the proxy layer: RFC 9421 request signing, Redis L2 cache (v0.27.92), and security header handling improvements (v0.27.88) suggest a consistent push toward production-grade security primitives without architectural breaks. The performance improvements in v0.27.95 address real-world Kubernetes clusters where large RouteGroup counts are common.

◆ Prediction

RFC 9421 support will likely get expanded configuration options — signing key rotation, policy enforcement modes, per-route key selection — as Zalando's internal adopters surface operational requirements for the filter.

Alternatives to runc and Skipper

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 runc or Skipper.

See all runc alternatives → · See all Skipper alternatives →

Recent activity from runc and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 7h agoSkipperv0.27.97
  2. 8h agoSkipperSkipper adds native RFC 9421 HTTP Message Signatures filter
  3. 1d agoSkipperCross-RouteGroup parse cache cuts load time 21%, memory 12%
  4. 1d agoSkipperv0.27.94
  5. 1d agoSkipperv0.27.93
  6. 7d agoSkipperSkipper adds Redis as L2 cache storage alongside existing Valkey
  7. 2mo agorunctmpfs regression on Ubuntu 20.04 kernels fixed
  8. 2mo agoruncrunc 1.5.0 stable, with dated support windows for older branches
  9. 3mo agoruncCVE-2026-41579: /dev symlink host write access fixed
  10. 3mo agoruncRelease candidate carrying the CVE-2026-41579 fix
  11. 3mo agoruncCVE-2026-41579 fix backported to the 1.4 branch
  12. 5mo agoruncBuild fixes and seccomp WaitKillableRecv support

Frequently asked questions

What is the difference between runc and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 runc better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 runc?

Top runc alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "runc alternatives" section above for the current picks, or visit /alternatives/runc for the full list with editorial commentary on each.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.