Authelia
Authelia ships weekly OIDC patches as v4.39 works through a long conformance backlog
A side-by-side editorial comparison of Icinga and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
Icinga 2 is fixing the same API permission holes across every supported branch.
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
Jackett ships daily indexer maintenance at a consistent one-release-per-day cadence.
Jackett is in a pure maintenance phase, shipping one point release per day focused on indexer domain migrations, category taxonomy updates, and selector fixes. The past 10 releases contain no new architectural work — only the routine churn of keeping 200+ indexers pointed at live domains. The cardigann engine received one correctness fix (false-positive redirect detection) but no new capabilities.
Icinga 2 ships security fixes as simultaneous releases across its 2.14, 2.15, and 2.16 branches, and has now done so twice in five weeks. The 18 August pair - v2.16.5 and v2.15.6, tagged 25 seconds apart - closes an events/* permission bypass on /v1/events and a memory-exhaustion path where a node could crash another using the 1 GB message limit, now capped at 16 MiB for messages from lower in the hierarchy. v2.16.5 additionally repairs an IcingaDB regression introduced in v2.16.0.
The recurring theme is that the API's filter and permission model was more permissive than intended. July's critical release introduced a filter-expression permission so DSL filters in API queries can be restricted per user, with enforcement deliberately deferred to v2.17; August's pair fixes filter expressions on /v1/events not being permission-checked at all. Cluster message handling is being tightened in parallel. The project is clearly working through an audit of the API surface, and it is backporting every finding rather than pushing users onto the newest branch.
Enforcement of the filter-expression permission is already scheduled for v2.17, so that release should be the one where the opt-in restrictions become mandatory - expect more backported API permission fixes across all three branches before it lands.
Jackett is in a pure maintenance phase, shipping one point release per day focused on indexer domain migrations, category taxonomy updates, and selector fixes. The past 10 releases contain no new architectural work — only the routine churn of keeping 200+ indexers pointed at live domains. The cardigann engine received one correctness fix (false-positive redirect detection) but no new capabilities.
The project is tracking toward indexer breadth maintenance rather than platform evolution. The addition of new private sites (0dayfiles, hdforever-api) broadens coverage, but the overarching motion is reactive — responding to indexer domain changes rather than building toward new functionality. Unless a contributor introduces a new scraping engine or protocol, this cadence is stable indefinitely.
The next releases will mirror the current cadence: daily domain bumps, occasional new private indexers, and cardigann edge-case fixes. No evidence of a broader architectural shift in the entries.
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 Icinga or Jackett.
Authelia ships weekly OIDC patches as v4.39 works through a long conformance backlog
Redocly ships full MCP server infrastructure—API docs are now directly AI-queryable
Kubernetes v1.37 promotes gang scheduling to Beta, closing the gap with dedicated ML schedulers.
Resend ships SSO and enters the enterprise conversation as its product surface broadens.
CircleCI ships an MCP server and auto-rollback deployments, moving well past pure CI.
GitHub Copilot splits into cost tiers and deepens agentic automation across the dev stack
See all Icinga alternatives → · See all Jackett alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Icinga and Jackett are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Icinga and Jackett are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Icinga alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Icinga alternatives" section above for the current picks, or visit /alternatives/icinga for the full list with editorial commentary on each.
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.