authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Scalar and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Scalar's mock server learns event-driven APIs while the reference UI picks up localization
Scalar ships as a monorepo, so the feed interleaves three release lines: the API reference (1.6x), the API client (1.1.x) and the mock server (0.1x). The June run brought AsyncAPI rendering to parity with dedicated tooling, added UI localization for seven languages with RTL handling, gave the client a requestBuilt hook for request signing, and taught the mock server to serve AsyncAPI documents over WebSocket and SSE.
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.
Scalar ships as a monorepo, so the feed interleaves three release lines: the API reference (1.6x), the API client (1.1.x) and the mock server (0.1x). The June run brought AsyncAPI rendering to parity with dedicated tooling, added UI localization for seven languages with RTL handling, gave the client a requestBuilt hook for request signing, and taught the mock server to serve AsyncAPI documents over WebSocket and SSE.
AsyncAPI is the clear investment across all three packages — rendered in the reference, filterable in navigation, and now mockable as live event streams. The client and reference lines otherwise trend toward extension points and polish rather than new surface.
Expect AsyncAPI support to complete the loop by reaching the API client, so event-driven APIs can be exercised interactively the way REST endpoints already are.
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.
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.
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.
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 Scalar or Skipper.
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 Scalar alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 6.3 vs 0.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.
Top Scalar alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Scalar alternatives" section above for the current picks, or visit /alternatives/scalar for the full list with editorial commentary on each.
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.