Insomnia
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
A side-by-side editorial comparison of Jackett and kOps — 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.
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
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.
kOps publishes alpha and beta tags rather than finals to this feed, with long commit lists dominated by provider-specific work. The 1.36 cycle removed Amazon Linux 2 support outright and changed omitted authorization to default to RBAC instead of AlwaysAllow. The 1.37 alpha continues along provider lines: Azure node identity now uses the IMDS attested metadata document, AWS reconciles target group health check changes on existing groups, GCE does the same for HTTP health checks, and Linode gained SSH key management.
Two patterns run through these tags. The first is reconciliation — kOps is closing the gaps where it created a resource but never re-checked it, which is what turns a provisioning tool into something that can be run continuously. The second is deliberate narrowing: dropping Amazon Linux 2 and defaulting authorization to RBAC both trade compatibility for a safer, smaller supported matrix.
The health check reconciliation pattern has now landed for AWS and GCE in the same cycle, so Azure and the smaller providers are the likely next targets.
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 kOps.
Insomnia's current work is Git, Cloud Sync and gRPC ergonomics — not headline features.
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
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 kOps 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 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jackett is currently shipping more aggressively (velocity 5.0 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.
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 kOps alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "kOps alternatives" section above for the current picks, or visit /alternatives/kops for the full list with editorial commentary on each.