authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Retool and werf — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The 3.x line finally ships function: authenticated secret writes and render patches.
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
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.
werf publishes the same work across alpha, beta, ea and stable channels plus a 3.x dev line, so one fix surfaces three or four times under different version numbers. This pair is that pattern exactly: v3.3.0 carries two features — writing authenticated secret values from deploy, and renderPatches support — plus four fixes, and v2.77.2 carries the same four fixes and nothing else. The fixes are the usual build-engine territory: buildah imports failing on symlinked paths, a panic when a stapel base image disappears mid-commit, a cache repo pointing at itself, and host-cleanup misreporting what it pruned.
The division of labour between the lines is now explicit — 2.x takes only fixes, 3.x takes fixes plus everything new. This is the first window where the 3.x dev line carries user-facing deploy function rather than build internals and gated experiments, which moves it from a place to accumulate changes toward something with its own reason to exist. The build-engine hardening under parallelism continues underneath both.
renderPatches and authenticated secret writes are both deploy-side, so the next 3.x releases likely continue there rather than returning to buildah. Whether the embedded deno work behind its build tag connects to the render path is still not stated.
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 Retool or werf.
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.
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Resend ships an API endpoint most days, and has just added the checkbox enterprises ask for
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Retool and werf are shipping at a similar cadence (velocity 5.0 vs 5.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. Retool and werf are shipping at a similar cadence (velocity 5.0 vs 5.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 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.
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.