Resend
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
A side-by-side editorial comparison of Skipper and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Skipper | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | reverse-proxy, kubernetes, http2, load-balancing | networking, zero-trust, kubernetes, multi-tenancy |
| Last editorial update | 18h ago | 15h ago |
| Website | Visit → | — |
Zalando's ingress proxy finally speaks HTTP/2 cleartext end to end
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
Tailscale is turning the tailnet itself into something a script provisions and pages through.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
Skipper ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.57, which enables h2c on the server handler, the proxy client, and the net client, with a new h2c:// route scheme and Kubernetes appProtocol wiring. Everything else in the window is Dependabot traffic and two narrow fixes to token introspection and grant auth.
The release cadence is a stream of small, individually unremarkable tags where the occasional protocol or load-balancing change is the only thing worth reading. Recent substance has clustered on the data path: leastRequests balancing in v0.27.53, h2c now. The auth filters are being maintained rather than extended, with fixes rather than new capability.
Expect the h2c work to generate follow-up fixes as it meets real gRPC backends, since the release notes already show HTTP Upgrade negotiation failing while direct prior knowledge works.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
Tailscale has spent this period on two different customers at once. The operator work serves platform teams running Tailscale inside Kubernetes, where the gaps being closed are reconciliation loops, stale DNS ConfigMaps and cert-renewal backoff. The tailnet API work serves a different shape entirely: organizations holding enough tailnets that a hundred is a page boundary, which only happens when tailnets are allocated per customer or per environment rather than per company. The second thread is the one that changes what Tailscale is for.
Pagination on list implies the creation API is being used at volume, so expect the alpha to gain the management operations a fleet needs — policy templating or bulk configuration across tailnets. The client release line looks settled on 1.102.x maintenance in the near term.
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 Tailscale.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
See all Skipper alternatives → · See all Tailscale alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — kubernetes — within Infra & APIs. Tailscale 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. Tailscale 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 Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.