DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Hotjar and Resend — release velocity, themes, recent moves, and the top alternatives to consider.
Hotjar's update feed stops in April 2025 — the arc it captures ended mid-sentence.
Hotjar's public update feed carries nothing newer than April 2025, and the entries it does carry arrive in duplicate pairs — a short stub and the full post, a few hours apart. What the archive shows is a product that spent 2024 and early 2025 expanding from passive observation (heatmaps, recordings) into active research: unmoderated User Tests, AI tagging of survey responses, and finally prototype testing.
Resend is wiring itself into every agent runtime it can reach, and now adding the controls to stop a send.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Hotjar's public update feed carries nothing newer than April 2025, and the entries it does carry arrive in duplicate pairs — a short stub and the full post, a few hours apart. What the archive shows is a product that spent 2024 and early 2025 expanding from passive observation (heatmaps, recordings) into active research: unmoderated User Tests, AI tagging of survey responses, and finally prototype testing.
The direction visible in these entries is a move up the research stack — from watching what users did on a live site toward asking them questions and testing designs before they ship. User Tests removed the moderator, AI tagging removed the manual sorting of open-ended responses, and prototype testing removed the requirement that the thing being tested exist yet. Each step cut a person out of the research loop. Whether that arc continued past April 2025 is not something this feed can answer.
No prediction is supportable from these entries. The feed has published nothing for over a year, so any claim about Hotjar's current direction would be invented rather than observed — the only honest read is that this channel has been abandoned or moved elsewhere.
Most recent entries are about who or what can call Resend rather than about email delivery itself: OAuth 2.1 with PKCE, a remote MCP server tracking the current spec, a Codex plugin, a one-click Claude connector, and support for the Agent Plugins Standard. The email product still gets attention — suppressions, template folders, a compatibility checker in the code editor, and now cancellation of scheduled or queued Broadcasts from the API. Entries are terse one-liners, so the shipping cadence reads faster than the surface area actually changing.
Resend is treating agents as the next class of sending client and building the authorization and discovery plumbing they need before that traffic arrives. The progression is legible: authenticate third parties (OAuth), be callable (MCP), be installable per vendor (Codex, Claude), then be installable by standard. The Cancel Broadcast API is the first sign of the next phase — once non-human callers can schedule sends, the ability to revoke one programmatically stops being a convenience.
Authorization and discovery are covered and reversibility has now started; the remaining gap is what an agent is permitted to send in the first place, so scoped per-agent sending limits or approval gates before dispatch are the natural next piece.
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 Hotjar or Resend.
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
NetBox adds a cooling data model — the first new infrastructure domain since power
See all Hotjar 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 0.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 0.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 Hotjar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hotjar alternatives" section above for the current picks, or visit /alternatives/hotjar 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.