Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Skipper and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
One pull request per version tag, and most of them are dependency bumps.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
Resend is turning an email API into something other people build products on.
Two months of releases split cleanly. One half is dashboard housekeeping — template folders, suppression management, Open Graph previews in the editor, Message-ID exposed on webhooks for threading. The other half is platform plumbing: a hosted MCP server, OAuth 2.1 with PKCE, a Claude connector, a Codex marketplace plugin, and automatic revocation of API keys leaked to GitHub.
Skipper cuts a release for essentially every merged pull request — six tags between 27 July and 7 August, each containing a single change. Two of the six are Dependabot bumps to CI actions and a fuzzing base image, two are test-only adjustments, and one fixes an error type assertion. Every entry carries the same boilerplate pointing at the multiarch image in GitHub's registry.
The visible work is maintenance of an already-stable proxy rather than feature development. What the test changes hint at is where the correctness concerns sit: an OPA policy test updated to explicitly deny truncated request bodies, because oversized JSON cannot be fully parsed and a policy that ignores input.truncated_body can be bypassed. That is authorization-under-load hardening, and it is the most interesting thing in the window even though it landed as a test.
The per-PR tagging rhythm will continue producing several versions a week regardless of change size. Readers tracking this product should expect the meaningful changes to be a small minority of the tags.
Two months of releases split cleanly. One half is dashboard housekeeping — template folders, suppression management, Open Graph previews in the editor, Message-ID exposed on webhooks for threading. The other half is platform plumbing: a hosted MCP server, OAuth 2.1 with PKCE, a Claude connector, a Codex marketplace plugin, and automatic revocation of API keys leaked to GitHub.
The center of gravity has moved from features a developer uses to interfaces another product consumes. OAuth is the hinge — with it, third parties can act on a user's Resend account without holding a key, which is the precondition for the connector and plugin distribution Resend is now shipping into Claude, Codex and Cursor. Tracking the 2026-07-28 MCP spec within nine days says they intend to stay current with that surface rather than treat it as a side project.
The pattern points to scoped OAuth permissions and a listing surface for third-party Resend apps, plus continued fast-following of MCP spec revisions. Nothing in these entries indicates a pricing or deliverability change.
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 Skipper or Resend.
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
A v5 release candidate train carrying a database migrator that has to work on the first try.
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
Three supported branches, patched in lockstep within the same minute.
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
See all Skipper alternatives → · See all Resend alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Resend is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Resend is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.
Top Resend alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Resend alternatives" section above for the current picks, or visit /alternatives/resend for the full list with editorial commentary on each.