authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Currents and ToolJet — release velocity, themes, recent moves, and the top alternatives to consider.
Currents moved into the IDE and repriced itself around self-serve in the same fortnight.
Currents publishes short labeled changelog entries, and the visible window runs from April to August. Two carry real weight: a VS Code and Cursor extension bringing CI runs, failure triage and Playwright traces into the editor, and a pricing restructure a week later adding a self-serve Business plan, cheaper rates, revised overage and yearly usage pooling. Around them sit integration work with Linear and Slack, and a @currents/playwright 2.0 release supporting Playwright 1.60 and newer.
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.
Currents publishes short labeled changelog entries, and the visible window runs from April to August. Two carry real weight: a VS Code and Cursor extension bringing CI runs, failure triage and Playwright traces into the editor, and a pricing restructure a week later adding a self-serve Business plan, cheaper rates, revised overage and yearly usage pooling. Around them sit integration work with Linear and Slack, and a @currents/playwright 2.0 release supporting Playwright 1.60 and newer.
Currents is moving its surface toward where failures get fixed rather than where they get reported. The IDE extension, the Linear integration and the Slack notifications all describe the same handoff, and each one names agents alongside humans as the consumer. The pricing change points the same way commercially: a self-serve Business tier removes the sales conversation from the middle of the funnel, and that is precisely the tier an IDE extension is most likely to pull in.
Expect the agent-facing framing to become explicit, with the IDE extension and the API growing structured failure output a coding agent consumes directly rather than prose written for a human reader.
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.
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.
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.
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 Currents or ToolJet.
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 Currents alternatives → · See all ToolJet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ToolJet is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. ToolJet is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.
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.