Parse Server
Parse Server racing through 9.10.2 alphas to close LiveQuery permission gaps and a crash-inducing security flaw.
Comparison · Infra & APIs
FireHydrant vs Jackett
A side-by-side editorial comparison of FireHydrant and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
FireHydrant vs Jackett: at a glance
What is FireHydrant?
On-call overrides now survive a schedule edit — and are the only way to change a shift.
FireHydrant shipped a real override layer for on-call schedules. Overrides now survive schedule edits made from either the web UI or the API, always win against an overlapping generated shift, can be stacked, and can be cancelled to restore the original system-generated shift. Reassignment, coverage requests, and shift deletion no longer mutate the generated schedule at all — each creates an override instead, which is what makes every change cleanly undoable. The constraint is historical: restoring a shift requires knowing what it originally looked like, and that data has only been tracked since 24 July 2026, so older rotations need a one-time regeneration first.
What is Jackett?
Jackett ships daily: tracker domain rotations, anti-bot patches, API indexer expansion
Jackett releases at least once per day, each touching a handful of tracker definitions. The work divides into three recurring categories: domain rotations for trackers that migrate addresses (52bt, magnetcat, world-torrent), category map corrections, and anti-bot switches that move scrapers to cookie-based auth when sites add reCaptcha. A first formal SECURITY.md was added in v0.24.2651, a minor governance step for a project that has been operating without one. The overall shape is maintenance, not development.
FireHydrant vs Jackett: editorial side-by-side
FireHydrant
2.5INFRA · APIS
On-call overrides now survive a schedule edit — and are the only way to change a shift.
◆ Current state
FireHydrant shipped a real override layer for on-call schedules. Overrides now survive schedule edits made from either the web UI or the API, always win against an overlapping generated shift, can be stacked, and can be cancelled to restore the original system-generated shift. Reassignment, coverage requests, and shift deletion no longer mutate the generated schedule at all — each creates an override instead, which is what makes every change cleanly undoable. The constraint is historical: restoring a shift requires knowing what it originally looked like, and that data has only been tracked since 24 July 2026, so older rotations need a one-time regeneration first.
◆ Where it's heading
The last year reads as one project — making an incumbent-grade on-call product safe enough to switch to. Customizable retrospective exports, authenticated status pages, consolidated analytics, an EU instance, MS Teams support, then the Signals Migrator that automates the move off PagerDuty and Opsgenie. Overrides fit the same pattern: a feature teams assume already exists, previously broken badly enough that admins learned not to touch a schedule once coverage was arranged. The work is closing table-stakes gaps ahead of a migration window, not opening new surfaces.
◆ Prediction
Expect the override model to be pushed out to the API and Terraform surfaces next, along with prompts to regenerate stale rotations before Opsgenie's April 2027 deletion date drives migration volume.
Jackett
5.0INFRA · APIS
Jackett ships daily: tracker domain rotations, anti-bot patches, API indexer expansion
◆ Current state
Jackett releases at least once per day, each touching a handful of tracker definitions. The work divides into three recurring categories: domain rotations for trackers that migrate addresses (52bt, magnetcat, world-torrent), category map corrections, and anti-bot switches that move scrapers to cookie-based auth when sites add reCaptcha. A first formal SECURITY.md was added in v0.24.2651, a minor governance step for a project that has been operating without one. The overall shape is maintenance, not development.
◆ Where it's heading
The most directional move in recent releases is the batch addition of private API-based indexers — v0.24.2644 added ten in one release (ptskit, oshenpt, kufei, ultrahd, zmpt, soulvoice, and others). API definitions are structurally more stable than HTML scrapers: no selector drift, no layout regressions. If this batch pace continues, it signals a deliberate effort to grow the private tracker catalog while reducing long-term maintenance overhead. Anti-bot hardening is the other observable trend: three of the six most recent releases include reCaptcha workarounds or FlareSolverr header fixes.
◆ Prediction
The next cluster of releases will continue domain rotations and category corrections at the current daily cadence. The API indexer batch pattern suggests another batch of private trackers within two to three weeks. Anti-bot patches will keep appearing as more trackers adopt CAPTCHA gates.
Alternatives to FireHydrant and Jackett
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 FireHydrant or Jackett.
GitHub
GitHub Copilot adds Claude Opus and memory-aware security autofix, deepening its agentic platform play.
Railway
Railway's weekly cadence is building a PaaS for AI agents: MCP, Cloud Agents, no-barrier entry.
Redocly
Redocly ships consent controls and closes an RBAC gap in its AI-powered docs platform
Skipper
Skipper fixes two silent data-loss bugs — body truncation on large requests and multi-value header drops.
ToolJet
ToolJet ships Custom Component Library and tightens enterprise controls on path to AI-native low-code.
See all FireHydrant alternatives → · See all Jackett alternatives →
Recent activity from FireHydrant and Jackett
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 16h agoJackettNew German tracker, freeleech toggle, anti-reCaptcha cookie switch
- 1d agoJackett0dayfiles category update, CodeQL dependency bump
- 2d agoJackettFix 403 on FlareSolverr-routed indexers with missing headers
- 3d agoJackettDomain rotations, category fixes, systemd install script fix
- 4d agoJackettNew xloli indexer, reCaptcha cookie switch, first SECURITY.md
- 5d agoJackettTen new private API indexers added in one batch
- 27d agoFireHydrantIntroducing: Preserved OnCall Schedule Overrides
- 2mo agoFireHydrantICYMI: The New In-App Signals Migrator ⚡
- 3mo agoFireHydrantA Better View of Your Team, Right From the Start
- 3mo agoFireHydrantMay Recap: Deeper Analytics, Smarter On-Call Filters & More
- 4mo agoFireHydrantApril Recap: EU Instance, MS Teams Scribe, and more!
- 6mo agoFireHydrantConsolidated Analytics Pages and Copy Retrospective to Markdown
Frequently asked questions
What is the difference between FireHydrant and Jackett?
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.
Is FireHydrant better than Jackett?
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.
What are the best alternatives to FireHydrant?
Top FireHydrant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FireHydrant alternatives" section above for the current picks, or visit /alternatives/firehydrant for the full list with editorial commentary on each.
What are the best alternatives to Jackett?
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.