ToolJet
ToolJet runs two release trains at once, and neither has changed direction in months
A side-by-side editorial comparison of Hotjar and werf — 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.
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.
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.
werf publishes the same work across alpha, beta, ea, and stable channels plus a 3.x dev line, so a single fix surfaces three or four times under different version numbers. The substance in this window is almost entirely build-engine concurrency: parallel recovery failures, races in Dockerfile builds, concurrent stderr access, serialized base image pulls, retries when a cached image id goes missing. New function is thin — a case-insensitive-condition-tracking feature gate, a build time summary in debug mode, and a registry-side cleanup report.
The 3.x dev line is accumulating what 2.x is stabilizing, and the one genuinely new thing in it is a deno binary embedded into werf releases behind a build tag. That is the only entry pointing anywhere beyond maintenance, and it is gated, so its intent is not yet stated. Otherwise the pattern is a mature build tool hardening buildah paths under parallelism, which is where self-hosted CI hits it hardest.
The embedded deno work is the thread to watch — if it stays behind its build tag it is an experiment, and if 3.x ships it on by default it implies a scripting surface for deployment.
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 werf.
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
Nexus does the diagnosis; the rest is on-call plumbing
1.38.4 is a security release in all but name, closing ACL gaps across the API.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.