Skipper
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
A side-by-side editorial comparison of Buildkite and Jackett — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Buildkite | Jackett |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 8.8 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | ci-cd, developer-tools, mcp, observability | indexers, torrent-search, maintenance, daily-releases |
| Last editorial update | 11h ago | 1h ago |
| Website | — | Visit → |
Buildkite keeps converting hand-rolled agent workarounds into first-class CI primitives.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
Daily tags chasing tracker domain moves, login changes and freeleech detection
Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.
Buildkite is shipping on two fronts. For agents, the MCP server gained list_tests for suite-wide reliability and duration metrics, and the Test Engine API returns the same aggregates behind a version header. For humans, a native checkout block moved sparse clones, shallow depth and skip-checkout out of plugins and into pipeline YAML, agents can ship job logs to an OpenTelemetry collector, and an organization-wide banner now says when GitHub API rate limits - not Buildkite - are holding up pull request status.
Buildkite is arguing that CI should be forge-independent, and backing it with coverage: GitHub, GitLab, Bitbucket, and now Cursor's Origin, where it shipped as a launch partner on day one. The agent-facing work follows one pattern - remove the workaround automation used to need, so aggregated test metrics replace assembling individual runs and a rate-limit banner replaces guessing why a status never arrived. Each release turns a behavior teams hand-rolled into a supported primitive.
The read side of the MCP server is now largely covered, so expect write-side tools next - retrying jobs, unblocking builds, editing pipelines from an agent - following the pattern the REST expansion established.
Jackett continues to ship a tag most mornings, each one a short auto-generated commit list of indexer definition edits. The newest adds a cookie login variant for HD-Space and captcha-aware login for funfile; the day before was a sweep of domain bumps and download-volume-factor detection corrections across torrenttip, magnetcat, 52bt, torrenteros, tocashare and seedcore. No release in this window touches the application itself.
This is maintenance as a product, and the cadence is the feature. Trackers rotate domains, add captchas, switch to cookie auth or vary their freeleech percentages, and Jackett absorbs each change within a day — Scenetime was added and dropped within days, 720pier removed and then restored by revert. The recurring shift from form login to cookie and captcha handling across sites is the one visible pattern: the definitions are steadily taking on more anti-bot handling.
Expect the same daily cadence of definition edits, with more cookie and captcha login variants as trackers tighten access. The entries show no application-level work planned or in progress.
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 Buildkite or Jackett.
Skipper trims a 4x memory regression out of routesrv, days after shipping h2c
CloudStack ships two LTS branches in lockstep and publishes nothing but pointers
Kinsta is moving MyKinsta's controls into its API, one surface per month
Verdaccio's 7.0 line is subtraction — forks dropped, toolchain swapped, tags mostly empty
Observability lands on OpenTelemetry semconv in the LTS train
Canvas agents gain memory, and onboarding moves into the editor
See all Buildkite 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. Buildkite is currently shipping more aggressively (velocity 8.8 vs 5.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. Buildkite is currently shipping more aggressively (velocity 8.8 vs 5.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 Buildkite alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Buildkite alternatives" section above for the current picks, or visit /alternatives/buildkite 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.