Windmill
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
A side-by-side editorial comparison of Jackett and Casdoor — release velocity, themes, recent moves, and the top alternatives to consider.
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Jackett ships a tagged release essentially every day, and every one of them is the same shape: tracker selectors updated, domains bumped, categories added, dead sites removed. The release notes are auto-generated commit lists with no prose. The C# application itself is stable; what changes is the YAML definition corpus that keeps a few hundred torrent trackers reachable through a single Torznab endpoint.
Nine releases in four days, all of them small — Casdoor is grinding on tenant-level governance.
Casdoor is running an unusually tight release train: nine tagged versions between August 1 and August 4, each carrying one or two commits. The content clusters around two areas. Retention and expiry are becoming per-organization settings — configurable record retention days, configurable token retention days, and automatic permission revocation after a set expiry. Separately, OAuth conformance work continues, with the RFC 8707 resource parameter now preserved through both the consent flow and the fast auto-signin path, plus a backchannel logout URL field on the application edit page.
Jackett ships a tagged release essentially every day, and every one of them is the same shape: tracker selectors updated, domains bumped, categories added, dead sites removed. The release notes are auto-generated commit lists with no prose. The C# application itself is stable; what changes is the YAML definition corpus that keeps a few hundred torrent trackers reachable through a single Torznab endpoint.
This is maintenance-as-product, and the cadence is a symptom rather than a sign of momentum: trackers move domains, add anti-bot checks, and change markup, so the definitions decay continuously and the fix rate has to match. The visible trend across these releases is attrition — torr9, rockbox, rain, runtheframes, torrentleech-pl and elitetorrent-wf all removed in a single fortnight — partially offset by category expansion on the trackers that survive.
Expect the daily definition-churn cadence to continue unchanged, with the removal list growing faster than the addition list. Nothing in these entries indicates work on the application core.
Casdoor is running an unusually tight release train: nine tagged versions between August 1 and August 4, each carrying one or two commits. The content clusters around two areas. Retention and expiry are becoming per-organization settings — configurable record retention days, configurable token retention days, and automatic permission revocation after a set expiry. Separately, OAuth conformance work continues, with the RFC 8707 resource parameter now preserved through both the consent flow and the fast auto-signin path, plus a backchannel logout URL field on the application edit page.
The per-organization retention and expiry settings point at multi-tenant deployments where each tenant carries its own compliance obligations — a single global retention policy stops working once one organization's auditor wants 90 days and another's wants 400. The RFC 8707 work is narrower but pointed: resource indicators bind a token to the API it was issued for, which matters when one identity provider fronts many services. A batch UpdatePermissions API added to cut Casbin enforcer rebuilds suggests some deployments are large enough that permission writes had become a bottleneck.
The retention-and-expiry pattern is not finished — record and token retention are now per-organization, and other lifecycle settings are the obvious next candidates. Expect the release cadence to stay at this granularity, since these tags carry single commits rather than batched releases.
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 Casdoor.
Windmill absorbed dbt, un-gated its warehouse languages, and turned AI authoring on by default.
Resend spent a month making itself something agents and third-party apps can log into.
Prowler turned its assistant from a read-only explainer into something that can change your tenant.
NetBox is spending 4.6 paying down query cost, not adding models.
Depot is no longer a build accelerator — it is assembling the whole CI stack underneath itself.
Buildkite is rebuilding its MCP server around what an agent actually does with a failed build.
See all Jackett alternatives → · See all Casdoor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jackett and Casdoor 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. Jackett and Casdoor 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 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 Casdoor alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Casdoor alternatives" section above for the current picks, or visit /alternatives/casdoor for the full list with editorial commentary on each.