Casdoor
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
A side-by-side editorial comparison of Skipper and Kata Containers — release velocity, themes, recent moves, and the top alternatives to consider.
One pull request per version tag, and most of them are dependency bumps.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
Kata rewrote its runtime in Rust and made it the default in 4.0.0
Kata Containers ships monthly, and the 3.2x series was steady infrastructure work — confidential computing plumbing for TDX and SEV-SNP, s390x block and memory hotplug, GPU coldplug, vCPU pinning, and a long tail of CI and packaging fixes. That series was also quietly staging a replacement: nearly every release carries runtime-rs commits alongside the Go runtime. 4.0.0 completes the handover, shipping the Rust runtime as the default.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
The visible work is maintenance of an already-stable proxy rather than feature development. What the test changes hint at is where the correctness concerns sit: an OPA policy test updated to explicitly deny truncated request bodies, because oversized JSON cannot be fully parsed and a policy that ignores input.truncated_body can be bypassed. That is authorization-under-load hardening, and it is the most interesting thing in the window even though it landed as a test.
The per-PR tagging rhythm will continue producing several versions a week regardless of change size. Readers tracking this product should expect the meaningful changes to be a small minority of the tags.
Kata Containers ships monthly, and the 3.2x series was steady infrastructure work — confidential computing plumbing for TDX and SEV-SNP, s390x block and memory hotplug, GPU coldplug, vCPU pinning, and a long tail of CI and packaging fixes. That series was also quietly staging a replacement: nearly every release carries runtime-rs commits alongside the Go runtime. 4.0.0 completes the handover, shipping the Rust runtime as the default.
Two long arcs converge here. The rewrite arc replaces a Go runtime with runtime-rs across x86_64, aarch64 and s390x and across QEMU, Cloud Hypervisor and Dragonball, bringing a new block storage model with it. The confidential-computing arc — TDX ACPI support, SNP protection, Trustee attestation, measured-rootfs validation, guest memfd — is what the project is actually selling, and a memory-safe runtime is the natural foundation for a multitenant isolation boundary.
Expect the 4.x line to focus on closing the configuration and behavior gaps the release notes acknowledge for users migrating off the Go runtime, rather than adding new hypervisor or architecture support immediately.
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 Skipper or Kata Containers.
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
A virtualization manager coasting on backports, with releases years apart
The workflow engine keeps shipping weekly, and more of each release is Seqera plumbing
An RPKI validator that now treats its own attack surface as the product
Robusta's alpha train keeps widening what can push alerts in and where it can run.
See all Skipper alternatives → · See all Kata Containers alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
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.
Top Kata Containers alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kata Containers alternatives" section above for the current picks, or visit /alternatives/kata-containers for the full list with editorial commentary on each.