authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Railway and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
Railway dropped the signup wall and put its agents everywhere — dashboard, CLI, phone, chat.
Railway ships a weekly changelog, and two threads dominate it. The first is agents: Cloud Agents went to beta in early August, then became runnable and resumable across the dashboard, CLI, and iOS, gained Connectors that pull external tools into Agent chats, and now install as a plugin inside Grok Bot. The second is database durability — Redis and then MySQL services convert to highly available clusters with automatic failover, alongside automatic CVE patching for Postgres. Enterprise controls arrived in parallel with Access Groups and staged template review.
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.
Railway ships a weekly changelog, and two threads dominate it. The first is agents: Cloud Agents went to beta in early August, then became runnable and resumable across the dashboard, CLI, and iOS, gained Connectors that pull external tools into Agent chats, and now install as a plugin inside Grok Bot. The second is database durability — Redis and then MySQL services convert to highly available clusters with automatic failover, alongside automatic CVE patching for Postgres. Enterprise controls arrived in parallel with Access Groups and staged template review.
The August 21 release is the one that changes the shape of the business: sites and databases can be deployed with no account at all. Paired with agents reachable from a phone or a chat app, Railway is removing every step between wanting infrastructure and having it running, and betting the conversion happens after the deploy rather than before. The HA and CVE-patching work is the necessary counterweight — a platform courting casual and agent-driven deploys has to make the databases underneath survive without an operator watching.
Expect Cloud Agents to leave beta and more third-party assistant surfaces after the Grok Bot plugin, plus HA conversion extended to the remaining managed database types. How anonymous deploys are metered and eventually claimed is the open question this cadence will have to answer.
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.
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 Railway or Retool.
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 Railway alternatives → · See all Retool alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Railway is currently shipping more aggressively (velocity 6.3 vs 5.0), 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. Railway is currently shipping more aggressively (velocity 6.3 vs 5.0), 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 Railway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Railway alternatives" section above for the current picks, or visit /alternatives/railway for the full list with editorial commentary on each.
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.