Hotjar
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
A side-by-side editorial comparison of Jackett and Spacelift — release velocity, themes, recent moves, and the top alternatives to consider.
Jackett ships daily, and every release is tracker definitions chasing sites that moved
Jackett cuts a release most mornings, each one a batch of indexer definition edits generated straight from the commit log. The work is uniform: new alternate domains for trackers that relocated, category mappings added or corrected, selectors repaired after a site changed its markup, and the occasional indexer removed when it goes dark. Recent releases also switched two trackers to API key authentication and added a public DHT crawler to another.
Spacelift's AI stopped explaining infrastructure and started deploying it.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
Jackett cuts a release most mornings, each one a batch of indexer definition edits generated straight from the commit log. The work is uniform: new alternate domains for trackers that relocated, category mappings added or corrected, selectors repaired after a site changed its markup, and the occasional indexer removed when it goes dark. Recent releases also switched two trackers to API key authentication and added a public DHT crawler to another.
Nothing about the application itself is changing in this window — the engine is stable and the product is the definition catalog. That makes the cadence a maintenance signal rather than a development one: the release rate tracks how fast the tracker ecosystem churns its domains and layouts, not how fast Jackett is building. The only structural movement is individual trackers migrating from scraped HTML to native APIs, which reduces the breakage surface where it happens.
Expect the daily definition-maintenance cadence to hold unchanged, since it is driven by external site churn rather than a roadmap. Further trackers moving to torznab or API key authentication would gradually cut the selector-repair volume.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
The arc is easy to trace: Intent opened to everyone in December, Intelligence launched in March, an MCP server exposed the platform to outside assistants in May, and by July the AI is performing deployments rather than describing them. Running underneath is the governance work that makes that defensible — module sharing permissions, OIDC claims, SCIM — because an agent that can deploy is only sellable if the registry and the identity provider bound what it can reach. Terragrunt support and the plan-policy cleanup show the core IaC engine still being maintained rather than neglected for the AI work.
Deployment by name is the narrow case; the obvious next step is Intent handling multi-stack changes with policy checks in the loop, and the permission model being extended to describe what the AI specifically is allowed to deploy rather than what a user is.
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 Spacelift.
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Merge is becoming the governance layer for agent tool access, not just a unified data API.
Ten releases in a month, all pointed at making agent sandboxes safe to run in production.
After the 4.5.0 drag-and-drop release, Dashy has settled into translations and dependency patches
Quay ships nothing but CVE remediation, mirrored across two supported branches
See all Jackett alternatives → · See all Spacelift 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 Spacelift alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Spacelift alternatives" section above for the current picks, or visit /alternatives/spacelift for the full list with editorial commentary on each.