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 Cloudflare Tunnel and q2 — release velocity, themes, recent moves, and the top alternatives to consider.
cloudflared's release feed is checksums and nothing else — until a release has to warn you off itself.
The tunnel daemon ships on a calendar-versioned cadence, roughly two to four releases a month. Nine of the last ten release bodies contain only SHA256 checksums for the packaged binaries across amd64, arm64, 386, arm, FIPS Linux and the macOS and Debian/RPM packages; no changelog text accompanies them. Whatever changed in a given version is not discoverable from this feed.
After two releases pulling ahead, q2 spends v0.23.0 back on parity: light/dark theming.
q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.
The tunnel daemon ships on a calendar-versioned cadence, roughly two to four releases a month. Nine of the last ten release bodies contain only SHA256 checksums for the packaged binaries across amd64, arm64, 386, arm, FIPS Linux and the macOS and Debian/RPM packages; no changelog text accompanies them. Whatever changed in a given version is not discoverable from this feed.
The publishing pattern is stable and unlikely to change: release notes live elsewhere, and the feed functions as a distribution manifest. The one exception in this window is instructive — 2026.8.0 was amended after the fact to carry a known-issue warning, which is why it now carries a later timestamp than the 2026.8.1 release that superseded it. That is the only mechanism by which this feed communicates anything: a release gets edited when it turns out to be unsafe to run.
Expect continued checksum-only releases every two to three weeks, with substantive text appearing only when another regression forces a retroactive warning.
q2 is the Quarto team's Rust reimplementation of the publishing toolchain, shipping as a statically linked single binary with minisign-signed archives and a bundled Quarto Hub MCP server, still marked experimental and not production-ready. The cadence holds at roughly a release a day through mid-August, with raw commit logs standing in for curated notes. v0.22.0 was the break in the pattern — llms.txt site output and a live-share preview, the first capability the original toolchain does not have. v0.23.0 goes straight back to closing the parity gap, and does it at epic scale.
The light-dark epic is the shape of how this team retires a Quarto 1 feature: a design doc, then ThemeConfig growing a parsed dark variant, dual theme compilation with color-scheme emission, attributed stylesheet links, a color-mode toggle runtime, an accessibility-aware highlight-style reader, a brand light/dark seam, and an end-to-end verification pass against quarto-web before the docs land. One phase (D) was deferred with its options recorded rather than dropped. Around it, panel-tabset support lands, format.html.css is finally copied and rebased per page, and the llms companion output gains a link-format attribute so authors control where companion links point — the one thread tying this release back to the v0.22.0 work.
Expect the remaining Q1 parity items to keep setting the release agenda, with the deferred light-dark phase D and the freshly opened panel-tabset plan the two named strands most likely to fill the next few tags. npx distribution for the standalone Quarto Hub MCP bundle is still the only distribution item the notes explicitly call planned.
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 Cloudflare Tunnel or q2.
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 Cloudflare Tunnel alternatives → · See all q2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. q2 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. q2 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 Cloudflare Tunnel alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cloudflare Tunnel alternatives" section above for the current picks, or visit /alternatives/cloudflared for the full list with editorial commentary on each.
Top q2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "q2 alternatives" section above for the current picks, or visit /alternatives/q2 for the full list with editorial commentary on each.