authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Retool and StatusCake — 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.
StatusCake's changelog is half UI cleanup, half outage bulletins about other people's infrastructure.
The product work in this window is interface consolidation on an established uptime monitor: a simple test-creation form promoted from a subset of users to everyone, with automatic fallback to the advanced form when advanced options are in play, and a reworked Test Details page that splits incidents, uptime, response time, and history into tabs and lands you on the current incident when a test is down. Pausing a test now cancels queued down alerts and ends repeat alert chains. Interleaved with these are posts that are not releases at all — running commentary on name.com DNS failures and Cloudflare outages. The feed's newest entry is from February 2026.
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.
The product work in this window is interface consolidation on an established uptime monitor: a simple test-creation form promoted from a subset of users to everyone, with automatic fallback to the advanced form when advanced options are in play, and a reworked Test Details page that splits incidents, uptime, response time, and history into tabs and lands you on the current incident when a test is down. Pausing a test now cancels queued down alerts and ends repeat alert chains. Interleaved with these are posts that are not releases at all — running commentary on name.com DNS failures and Cloudflare outages. The feed's newest entry is from February 2026.
Nothing here changes what StatusCake monitors or how; it changes how quickly an operator gets to the thing that broke. The alert-suppression work and the default-to-current-incident landing both target the same complaint, which is noise during an event. The outage bulletins are worth reading as positioning rather than product — the company narrating third-party failures is claiming the observer's seat. Six months without a product entry means the direction here cannot be confirmed from the feed.
The stated multi-location regions rollout is the one concrete commitment in the window, and confirmation alerts across several locations is the obvious follow-on. Beyond that the feed is too stale to support a prediction.
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 StatusCake.
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 Retool alternatives → · See all StatusCake 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 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. Retool 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 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 StatusCake alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "StatusCake alternatives" section above for the current picks, or visit /alternatives/statuscake for the full list with editorial commentary on each.