authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Redocly and Retool — release velocity, themes, recent moves, and the top alternatives to consider.
Redocly opens its docs MCP endpoint to anonymous readers
Redocly publishes a per-package changelog across a wide surface — Realm, Reef, Revel, Reunite, Redoc, the theme and config packages — so a single upstream fix appears as six or seven near-identical entries on the same timestamp. The newest substantive item is a single config feature: mcp.docs.publicEndpoint, which exposes a documentation MCP endpoint to anonymous users. Around it sit Reunite app changes for organization invites and project card badges, and a batch of packages all republished for one missing dependency export.
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.
Redocly publishes a per-package changelog across a wide surface — Realm, Reef, Revel, Reunite, Redoc, the theme and config packages — so a single upstream fix appears as six or seven near-identical entries on the same timestamp. The newest substantive item is a single config feature: mcp.docs.publicEndpoint, which exposes a documentation MCP endpoint to anonymous users. Around it sit Reunite app changes for organization invites and project card badges, and a batch of packages all republished for one missing dependency export.
Two things are visible in this feed. The first is the packaging: because every package cuts its own version for a shared fix, the changelog overstates activity and buries the one release that carries a feature. The second is where the features land — documentation as something machines consume, with the MCP endpoint now reachable without a login. The config package is where that gets switched on, which is a reasonable signal that the capability is being pushed toward self-serve adoption rather than kept behind account setup.
Expect the MCP surface to accumulate configuration rather than announcements — scoping, rate limiting, or which docs the endpoint exposes — since that is the shape every feature on this feed arrives in.
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 Redocly 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 Redocly 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. Redocly and Retool 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. Redocly and Retool 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 Redocly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Redocly alternatives" section above for the current picks, or visit /alternatives/redocly 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.