Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
A side-by-side editorial comparison of Jackett and Kubeshark — release velocity, themes, recent moves, and the top alternatives to consider.
A daily patch cycle keeping several hundred tracker definitions from going stale.
Jackett ships a build essentially every morning, and each one is the same kind of work: tracker definitions re-pointed at moved domains, CSS selectors repaired after a site redesign, category mappings corrected, and dead indexers deleted. The last ten releases removed six trackers outright (chilebt, FilmesHdTorrent, torr9, rain, runtheframes, elitetorrent-wf) while adding native torznab API support for pornotorrent and private-tracker handling for simurg. The changelogs are auto-generated commit lists, so the release notes are the commit subjects.
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
Jackett ships a build essentially every morning, and each one is the same kind of work: tracker definitions re-pointed at moved domains, CSS selectors repaired after a site redesign, category mappings corrected, and dead indexers deleted. The last ten releases removed six trackers outright (chilebt, FilmesHdTorrent, torr9, rain, runtheframes, elitetorrent-wf) while adding native torznab API support for pornotorrent and private-tracker handling for simurg. The changelogs are auto-generated commit lists, so the release notes are the commit subjects.
This is maintenance as the product, and the churn rate is the signal worth watching. Indexer definitions decay continuously because the sites behind them move domains, change markup, and disappear, so Jackett's value is the speed of the repair loop rather than any feature roadmap. The removals slightly outpace the additions across this window, which is the normal shape for a catalog tracking sites that go dark. Where real capability does appear it is narrow and per-indexer — a native API adopted here, freeleech parsing corrected there.
Expect the daily cadence and the same mix to continue: domain bumps and selector repairs as the bulk, a handful of indexer removals, and occasional per-site API or category work. Nothing in these entries points to a structural change in how definitions are maintained.
Kubeshark is mid-transition from V1 to V2, announced for January 2026. The v52.11.0 release rewrote the backend entirely — V2 runs on the new implementation while V1 stays on the legacy one — and added cluster-wide L4 PCAP export plus L7-to-L4 mapping that ties API calls back to the TCP and UDP connections carrying them. Since then the releases have been smaller: connectivity map performance, per-flow PCAP files in snapshot archives, and a migration of every service domain from kubehq.com to kubeshark.com.
The product is moving down the stack. It started as an API-level traffic viewer and the recent work is all about L4 — connectivity maps, raw PCAP export, mapping L7 calls onto the connections beneath them — which puts it closer to a cluster-wide packet capture tool than a service-mesh observability dashboard. The licensing is moving in the opposite direction of the feature set: an almost-unlimited complimentary licence through the end of 2025 was replaced by one capped at 100 nodes, so the free tier is being defined rather than left open. Two releases also mention agentic infrastructure being staged but not yet usable.
Expect V2 to consolidate onto the new backend and the legacy V1 path to be dropped once the transition completes, since the release notes already describe V1 as being sunset. The staged agentic infrastructure is the most likely candidate for the next substantive feature, given it has been shipped inert twice.
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 Jackett or Kubeshark.
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all Jackett alternatives → · See all Kubeshark alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jackett 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. Jackett 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 Jackett alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jackett alternatives" section above for the current picks, or visit /alternatives/jackett for the full list with editorial commentary on each.
Top Kubeshark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Kubeshark alternatives" section above for the current picks, or visit /alternatives/kubeshark for the full list with editorial commentary on each.