Tailscale
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
A side-by-side editorial comparison of Hotjar and Spacelift — 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.
Spacelift's AI stopped explaining infrastructure and started deploying it.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
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.
The dated window ends in March with Spacelift Intelligence, first-class Terragrunt support, OIDC subject claim customisation and a self-service Templates release. Everything since sits in undated rows and is the more consequential half: a remote MCP server in May, SCIM 2.0 provisioning in June, and in July the ability to ask Intelligence to deploy a module by name, resolved against the Module Registry. An August notice warns that the API will start returning HTTP 500 on internal errors instead of 200.
The arc is easy to trace: Intent opened to everyone in December, Intelligence launched in March, an MCP server exposed the platform to outside assistants in May, and by July the AI is performing deployments rather than describing them. Running underneath is the governance work that makes that defensible — module sharing permissions, OIDC claims, SCIM — because an agent that can deploy is only sellable if the registry and the identity provider bound what it can reach. Terragrunt support and the plan-policy cleanup show the core IaC engine still being maintained rather than neglected for the AI work.
Deployment by name is the narrow case; the obvious next step is Intent handling multi-stack changes with policy checks in the loop, and the permission model being extended to describe what the AI specifically is allowed to deploy rather than what a user is.
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 Spacelift.
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Merge is becoming the governance layer for agent tool access, not just a unified data API.
Ten releases in a month, all pointed at making agent sandboxes safe to run in production.
After the 4.5.0 drag-and-drop release, Dashy has settled into translations and dependency patches
Jackett ships daily, and every release is tracker definitions chasing sites that moved
Quay ships nothing but CVE remediation, mirrored across two supported branches
See all Hotjar alternatives → · See all Spacelift alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hotjar and Spacelift are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Hotjar and Spacelift are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 Spacelift alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Spacelift alternatives" section above for the current picks, or visit /alternatives/spacelift for the full list with editorial commentary on each.