authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Home Assistant vs ToolJet
A side-by-side editorial comparison of Home Assistant and ToolJet — release velocity, themes, recent moves, and the top alternatives to consider.
Home Assistant vs ToolJet: at a glance
What is Home Assistant?
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.
What is ToolJet?
ToolJet is paying the migration bill for the Git branching it just shipped.
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
Home Assistant vs ToolJet: editorial side-by-side
Home Assistant
3.8INFRA · APIS
Home Assistant is systematically removing the technical knowledge its own product used to require.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
ToolJet
6.3INFRA · APIS
ToolJet is paying the migration bill for the Git branching it just shipped.
◆ Current state
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
◆ Where it's heading
Two threads run through this feed. The first is enterprise governance — branching, permissions, restrict-query-run, personal access tokens — which lands in beta and then crosses to LTS. The second is per-connector AI query generation, added to data sources individually rather than as one assistant. Right now the governance thread dominates and is in its consolidation phase: a data-model change of this size is followed by weeks of migration fixes before the LTS crossing is safe.
◆ Prediction
The near-term releases should stay corrective until the migration path is stable, with the Git sync phase 2 work crossing into the LTS line once the fresh-install and upgrade failures stop recurring.
Alternatives to Home Assistant and ToolJet
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 ToolJet.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Home Assistant alternatives → · See all ToolJet alternatives →
Recent activity from Home Assistant and ToolJet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoToolJetBackground processing and migration handling refactored
- 2d agoToolJetFix: migration lock contention broke fresh installs and upgrades
- 2d agoToolJetFix: database connection handling in migration scripts
- 5d agoToolJetGit sync phase 2: branching, unsynced resources and GitLab ⚡
- 7d agoToolJetStartup no longer hard-fails when the RDS cert download is blocked
- 7d agoToolJetPersonal access tokens arrive in the LTS line
- 28d agoHome AssistantHome Assistant drops the :8123 port for new installs ⚡
- 2mo agoHome AssistantPurpose-built automation triggers graduate from Labs to default ⚡
- 3mo agoHome AssistantCard picker suggests cards from what you want to show
- 3mo agoHome AssistantPublic roadmap and rebuilt templating documentation
- 5mo agoHome AssistantInfrared devices become first-class in Home Assistant
Frequently asked questions
What is the difference between Home Assistant and ToolJet?
They serve adjacent needs but don't currently overlap on shipped themes. ToolJet is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 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.
Is Home Assistant better than ToolJet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. ToolJet is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 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.
What are the best alternatives to Home Assistant?
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.
What are the best alternatives to ToolJet?
Top ToolJet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ToolJet alternatives" section above for the current picks, or visit /alternatives/tooljet for the full list with editorial commentary on each.