authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Redocly vs werf
A side-by-side editorial comparison of Redocly and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Redocly vs werf: at a glance
What is Redocly?
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.
What is werf?
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.
Redocly vs werf: editorial side-by-side
Redocly
5.0INFRA · APIS
Redocly opens its docs MCP endpoint to anonymous readers
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
werf
5.0INFRA · APIS
The 3.x line finally ships function: authenticated secret writes and render patches.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Redocly and werf
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 werf.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all Redocly alternatives → · See all werf alternatives →
Recent activity from Redocly and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agowerf3.3.0 adds authenticated secret writes and renderPatches to deploy
- 1d agowerf2.77.2 backports four build and cleanup fixes, no new function
- 2d agoRedoclyPublic MCP docs endpoint for anonymous users
- 5d agoRedoclyVisibility badges on project cards
- 5d agoRedoclyPending organization invites surfaced inside the app
- 8d agoRedoclyReef: missing @xyflow/system exports fixed
- 8d agoRedocly@redocly/graphql-docs: missing @xyflow/system exports fixed
- 8d agoRedocly@redocly/asyncapi-docs: missing @xyflow/system exports fixed
- 22d agowerf2.77.1 fixes buildah imports on symlinked paths
- 22d agowerf3.x dev embeds deno and adds a registry-side cleanup report
- 23d agowerf2.76.0 adds condition-tracking gate and build timing
- 27d agowerflatest-signature
Frequently asked questions
What is the difference between Redocly and werf?
They serve adjacent needs but don't currently overlap on shipped themes. Redocly and werf 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.
Is Redocly better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Redocly and werf 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.
What are the best alternatives to Redocly?
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.
What are the best alternatives to werf?
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.