authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Stacker and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Stacker's AI agent has absorbed every part of app building except the data itself.
Stacker builds internal tools and customer portals on top of existing data. From late October 2025 the entire changelog is one project: an AI Builder Agent that generates and edits apps by conversation. In under seven weeks it went from generating initial pages and layouts to editing tables and fields, creating lookups, rollups and formulas, reshaping create forms, reordering navigation, building white-labelled external portals with custom domains and permissions, and finally taking a spreadsheet upload and configuring a schema and matching layouts from it.
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.
Stacker builds internal tools and customer portals on top of existing data. From late October 2025 the entire changelog is one project: an AI Builder Agent that generates and edits apps by conversation. In under seven weeks it went from generating initial pages and layouts to editing tables and fields, creating lookups, rollups and formulas, reshaping create forms, reordering navigation, building white-labelled external portals with custom domains and permissions, and finally taking a spreadsheet upload and configuring a schema and matching layouts from it.
The sequencing is deliberate: each release hands the agent one more thing that previously required the no-code editor, while the company repeatedly reassures users that the full editor still works on AI-built apps. That dual framing — build by conversation, refine by hand — is the position Stacker is defending, and it is a reasonable answer to pure prompt-to-app tools that leave nothing to adjust afterwards. The portal release is the notable widening, since it points the agent at the external-user product rather than internal tools.
Every surface except data connection has now been handed to the agent; connecting and mapping an external source — the step still done manually before any of this works — is the remaining gap, and the spreadsheet uploader is the first move toward closing it.
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 Stacker 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.
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Stacker alternatives → · See all werf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. werf is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Stacker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Stacker alternatives" section above for the current picks, or visit /alternatives/stacker 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.