Jackett
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
A side-by-side editorial comparison of JuiceFS and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
JuiceFS is spending its v1.4 cycle on metadata-engine efficiency, one transaction at a time.
The v1.4 cycle is running in the open across three pre-releases — beta1 in May with 373 commits since v1.3, beta2 two weeks later, and rc1 in June. The recurring subject is the metadata layer: quota keys no longer create mass tombstones, quota lookups are batched to save a round trip, transactional key-value lookups collapse into a single transaction, and chunks commit in write order. Feature additions are narrow — custom tags in tier configuration, an upload-part stream API, and checkpoint support for multipart uploads in sync.
Skipper now serves zone-filtered routes only when its own ingress is balanced across zones.
Skipper, Zalando's HTTP router and Kubernetes ingress, tags a release for nearly every merge, so most entries are dependency bumps. The substantive ones this autumn are about zone-aware routing: v0.28.56 made routesrv recompress only zones whose routes changed, and v0.28.60 on November 2 serves zone-filtered routes only when skipper-ingress is balanced across zones, falling back to the global table otherwise.
The v1.4 cycle is running in the open across three pre-releases — beta1 in May with 373 commits since v1.3, beta2 two weeks later, and rc1 in June. The recurring subject is the metadata layer: quota keys no longer create mass tombstones, quota lookups are batched to save a round trip, transactional key-value lookups collapse into a single transaction, and chunks commit in write order. Feature additions are narrow — custom tags in tier configuration, an upload-part stream API, and checkpoint support for multipart uploads in sync.
This is a release cycle about cost at scale rather than new capability. Every metadata change removes a round trip, a tombstone, or a transaction from paths that run constantly, which is where a filesystem backed by object storage and an external metadata engine actually gets expensive. The sync and upload work points the same direction: multipart and streaming paths make large-object transfers resumable instead of restarting them. Contributor counts stay high across releases, so the pace is sustained rather than a push by one maintainer.
With rc1 cut and the changes since beta2 already down to 50 commits, a v1.4.0 final is the likely next step rather than further feature work.
Skipper, Zalando's HTTP router and Kubernetes ingress, tags a release for nearly every merge, so most entries are dependency bumps. The substantive ones this autumn are about zone-aware routing: v0.28.56 made routesrv recompress only zones whose routes changed, and v0.28.60 on November 2 serves zone-filtered routes only when skipper-ingress is balanced across zones, falling back to the global table otherwise.
Zone-aware routing is being made safe for production, with guards against skew and fixes for a data race and silent misconfiguration. It currently works only in the routesrv mode, and the release notes say the direct Kubernetes mode needs the same filtering.
Expect zone filtering to be extended to the skipper-to-Kubernetes mode in a coming tag, as the v0.28.60 notes say is needed.
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 JuiceFS or Skipper.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
OctoPrint 2.0 is on its seventh release candidate, still with no final date.
Quarto's VS Code extension moved to MIT and now ships fixes for Positron and citations.
Gitea has switched to version 28 numbering; its feed has caught only the dev tags.
rsyslog keeps adding cloud outputs, with Kinesis in October after CloudWatch in August.
KubeVirt 1.10 reaches beta with 1,345 changes from 94 contributors.
See all JuiceFS alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — performance — within Infra & APIs. Skipper 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper 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.
Top JuiceFS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JuiceFS alternatives" section above for the current picks, or visit /alternatives/juicefs for the full list with editorial commentary on each.
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.