authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Redocly vs Skipper
A side-by-side editorial comparison of Redocly and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Redocly vs Skipper: 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 Skipper?
Skipper tags a release per commit, so four versions in an hour can mean one real change.
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
Redocly vs Skipper: 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.
Skipper
6.3INFRA · APIS
Skipper tags a release per commit, so four versions in an hour can mean one real change.
◆ Current state
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
◆ Where it's heading
Two kinds of change alternate on this feed: filter and backend capability arriving occasionally, and a continuous stream of dependency group bumps between them. The capability side has been concentrated on the proxy edge — OIDC claim handling, load-balancer algorithms, Valkey-backed state — while the performance work targets the route data path itself. Because the tagging is per commit, cadence here says nothing about how much shipped.
◆ Prediction
Given the benchmark-driven optimisation in this batch, further allocation work on the eskip formatting and routing path is the most likely next capability change, with dependency bumps continuing to fill the tags between.
Alternatives to Redocly and Skipper
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 Skipper.
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.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Redocly alternatives → · See all Skipper alternatives →
Recent activity from Redocly and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoRedoclyPublic MCP docs endpoint for anonymous users
- 2d agoSkipperDependency: CodeQL scanning action bumped to 4.37.9
- 2d agoSkipperRoute formatting sheds redundant Sprintf calls: ~14% faster, ~16% fewer allocations
- 2d agoSkipperDependency: 15-package Go module group bump
- 2d agoSkipperAgent skill files renamed to match the specification
- 3d agoSkipperNew OIDC filter prunes oversized claim arrays before the cookie is written
- 5d agoRedoclyVisibility badges on project cards
- 5d agoRedoclyPending organization invites surfaced inside the app
- 6d agoSkipperValkey SetWithExpire becomes a single atomic command
- 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
Frequently asked questions
What is the difference between Redocly and Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 5.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.
Is Redocly better than Skipper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 6.3 vs 5.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.
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 Skipper?
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.