authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Redocly and ToolJet — 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.
ToolJet is paying the migration bill for the Git branching it just shipped.
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
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.
ToolJet runs two parallel release trains: an LTS line taking near-daily patches and a beta line where features land as large rollups. The beta line's headline release was Git sync phase 2, which put branching, unsynced-resource tracking, GitLab support and folder-level permissions into the product in one piece. The three tags since then are all migration and database-connection repair on that same change, including one where the shared migration transaction's locks made fresh installs and upgrades time out. On the LTS side the recent additions are narrower: personal access tokens and a startup fix for blocked RDS certificate downloads.
Two threads run through this feed. The first is enterprise governance — branching, permissions, restrict-query-run, personal access tokens — which lands in beta and then crosses to LTS. The second is per-connector AI query generation, added to data sources individually rather than as one assistant. Right now the governance thread dominates and is in its consolidation phase: a data-model change of this size is followed by weeks of migration fixes before the LTS crossing is safe.
The near-term releases should stay corrective until the migration path is stable, with the Git sync phase 2 work crossing into the LTS line once the fresh-install and upgrade failures stop recurring.
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 ToolJet.
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 ToolJet alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ToolJet 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. ToolJet 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 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 ToolJet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ToolJet alternatives" section above for the current picks, or visit /alternatives/tooljet for the full list with editorial commentary on each.