ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of Hotjar and incident.io — release velocity, themes, recent moves, and the top alternatives to consider.
Hotjar's update feed has gone quiet — the 2026 entries are share buttons, not releases.
The three most recent entries are not product updates at all: they are captures of the page's social share widget, carrying 'Copy link' as their title and a Facebook share dialog as their URL. Behind them, the newest genuine announcement is from April 2025, covering improvements to Surveys and User Tests including prototype testing. The substantive items below that date to 2024.
Nexus does the diagnosis; the rest is on-call plumbing
Investigations went generally available in early August: Nexus posts a root-cause hypothesis and its evidence into the incident channel within minutes of declaration. Around it the on-call layer keeps filling in — coverage policies that flag gaps in a rota, escalation reassignment, shift swapping, private incidents scoped to whole teams. Insights picked up 'match any' filtering, and MCP plus the macOS app reached GA in July.
The three most recent entries are not product updates at all: they are captures of the page's social share widget, carrying 'Copy link' as their title and a Facebook share dialog as their URL. Behind them, the newest genuine announcement is from April 2025, covering improvements to Surveys and User Tests including prototype testing. The substantive items below that date to 2024.
What the real entries show is a product that expanded from behavioural analytics into structured research — surveys, user tests, prototype testing, AI-tagged responses, and a path from survey respondent to follow-up interview. Whether that expansion has continued through 2026 cannot be told from this feed, because nothing since April 2025 has been captured with content.
There is not enough recent data to predict a next move. The feed's newest real announcement is more than a year old and the entries after it are page furniture, so any read on Hotjar's current direction would be invented rather than observed.
Investigations went generally available in early August: Nexus posts a root-cause hypothesis and its evidence into the incident channel within minutes of declaration. Around it the on-call layer keeps filling in — coverage policies that flag gaps in a rota, escalation reassignment, shift swapping, private incidents scoped to whole teams. Insights picked up 'match any' filtering, and MCP plus the macOS app reached GA in July.
The agent has moved from something you ask to something that acts the moment an incident opens, while everything else hardens the scheduling and escalation machinery beneath it. Coverage policies and vacation conflict checks point at an on-call product being pushed toward guarantees rather than rotas you hope are correct.
Expect Nexus to reach past the hypothesis into the work that follows it — suggested actions, post-incident drafting — and more policy checks that catch scheduling gaps before an incident finds them.
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 incident.io.
ToolJet runs two release trains at once, and neither has changed direction in months
Honeycomb bets that the agent, not the engineer, should notice the anomaly first
Jenkins is shrinking its own war file and rebuilding its UI, one weekly release at a time
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
1.38.4 is a security release in all but name, closing ACL gaps across the API.
See all Hotjar alternatives → · See all incident.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. incident.io 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. incident.io 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 incident.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "incident.io alternatives" section above for the current picks, or visit /alternatives/incident-io for the full list with editorial commentary on each.