authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Home Assistant and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
Home Assistant is systematically removing the technical knowledge its own product used to require.
Home Assistant ships monthly, and the last five releases read as one campaign: strip out the prerequisites that made the product feel like infrastructure. 2026.7 made purpose-specific automation triggers the default for everyone, so you describe what your home should do instead of which entity changes state. 2026.8 went further and removed the :8123 port from new installations, moved web server configuration out of YAML into the interface, and deleted the words advanced and expert from roughly 43 places. The capability surface is not shrinking; the vocabulary required to reach it is.
Retool posts one-line changelog entries, and its agent work is the only visible thread
Retool publishes very short changelog entries — most under 120 characters, several under 60 — so each release is a headline with a sentence attached. The recent run covers message queueing, branch management gaining rename and copy, performance work on the app building agent, a BigID resource deprecation, and periodic self-hosted stable tags. Nothing here carries enough text to judge scope, only direction.
Home Assistant ships monthly, and the last five releases read as one campaign: strip out the prerequisites that made the product feel like infrastructure. 2026.7 made purpose-specific automation triggers the default for everyone, so you describe what your home should do instead of which entity changes state. 2026.8 went further and removed the :8123 port from new installations, moved web server configuration out of YAML into the interface, and deleted the words advanced and expert from roughly 43 places. The capability surface is not shrinking; the vocabulary required to reach it is.
The pattern is consistent: take something that only worked if you already understood Home Assistant's internals, and re-express it in terms of the outcome the user wants. Triggers moved from entity-and-state to intent, the card picker moved from which card type to which thing in your home, and addressing moved from a memorized port to an ordinary web address. Each step ships with a migration that leaves existing installs untouched, which is how the project widens its audience without breaking the technical install base it already has. Integrations teaching the automation engine their own triggers is the piece with the most compounding left in it.
Expect the next releases to keep converting Labs experiments into defaults and to move the remaining YAML-only configuration surfaces into the interface, following the pattern the web server settings just set.
Retool publishes very short changelog entries — most under 120 characters, several under 60 — so each release is a headline with a sentence attached. The recent run covers message queueing, branch management gaining rename and copy, performance work on the app building agent, a BigID resource deprecation, and periodic self-hosted stable tags. Nothing here carries enough text to judge scope, only direction.
Two threads are legible from the headlines. The app building agent keeps getting attention, which is where Retool is putting its AI bet, and the branch-based development workflow keeps accruing the controls a team needs — renaming and copying branch names is small, but it is the kind of gap that only matters once people are actually working in branches. Deprecations like the BigID resource type suggest a periodic prune of connectors that did not find usage.
Branch controls have now been extended twice without a governance layer appearing, so expect permissions or review on branch operations next, since that is what teams ask for once branch-based development is in real use.
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 Home Assistant or Retool.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Alert rate limits stop being per-source and start being per-tenant, by query.
The essay series keeps running ahead of the products it describes.
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
The 3.x line finally ships function: authenticated secret writes and render patches.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Home Assistant alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Retool is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. Retool is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Home Assistant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Home Assistant alternatives" section above for the current picks, or visit /alternatives/home-assistant for the full list with editorial commentary on each.
Top Retool alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Retool alternatives" section above for the current picks, or visit /alternatives/retool for the full list with editorial commentary on each.