← Back to home
Comparison · Infra & APIs

authentik vs Skipper

A side-by-side editorial comparison of authentik and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.

authentik vs Skipper: at a glance

FeatureauthentikSkipper
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesidentity-provider, enterprise-agents, endpoint-identity, oauth2reverse-proxy, kubernetes, memory-footprint, zone-aware-routing
Last editorial update8h ago1h ago
WebsiteVisit →Visit →

What is authentik?

authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO

2026.8.0 is out, closing a seven-candidate train that ran through early August. The GA tag itself is the last cherry-pick batch — SCIM group membership removals, a proxy redirect that preserves query strings, session deletion on user deactivation — but the release it finalizes is where the substance lives: an Actors primitive in core, an enterprise Agent requiring a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.

Read the full authentik trajectory →

What is Skipper?

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

Read the full Skipper trajectory →

authentik vs Skipper: editorial side-by-side

A
authentik
INFRA · APIS
6.3

authentik 2026.8 ships: Actors, domain-joined Agents, and a push past browser-mediated SSO

◆ Current state

2026.8.0 is out, closing a seven-candidate train that ran through early August. The GA tag itself is the last cherry-pick batch — SCIM group membership removals, a proxy redirect that preserves query strings, session deletion on user deactivation — but the release it finalizes is where the substance lives: an Actors primitive in core, an enterprise Agent requiring a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.

◆ Where it's heading

Two threads converge in this major. The identity surface keeps broadening at the protocol edge — CAS, WS-Fed, token exchange delegation, on-behalf-of — while the enterprise tier grows an endpoint story that reaches machines and devices rather than browser sessions. The RC train's shape reinforces it: six candidates fired in one day on CI and docs, then one heavy candidate carrying the features, then a fix-only close. That is release engineering hardened around a major, not a routine point release.

◆ Prediction

With Agents and Actors now GA rather than cherry-picks, the next branch should build out what they enable — device-conditioned policies or agent-brokered credentials — while 2026.8.x settles into backport patches.

S
Skipper
INFRA · APIS
5.0

Skipper trims a 4x memory regression out of routesrv, days after shipping h2c

◆ Current state

Zalando's HTTP router ships patch tags almost daily, and most carry a single dependency bump or a one-line auth fix. The substance in this window is v0.27.63, which stops routesrv holding an uncompressed route tree alongside the compressed buffer: retained memory in the release's own benchmark falls from 30.7 MB to 2.0 MB, undoing most of the 4x increase zone-aware routing had introduced. Around it sit narrow auth repairs, and an eskip parser change that finally accepts negative numeric arguments in predicates and filters.

◆ Where it's heading

Two threads run through the recent tags. The data path keeps getting real work - leastRequests balancing, then h2c end to end in v0.27.57, now the memory cost of zone-aware routing being paid back. The auth filters, by contrast, are only being maintained: token introspection, grant auth, and now the OIDC Referer handling are fixes rather than new capability, and several are follow-ups to each other rather than independent bugs.

◆ Prediction

Zone-aware routing looks like the source of the recent memory attention, so expect further tuning around route storage and the hash computation done on every pull, which the release's second benchmark already isolates. The OIDC cookie change is the second link in an auth chain that started with the grant-auth fix, and is likely to draw another follow-up.

Alternatives to authentik 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 authentik or Skipper.

See all authentik alternatives → · See all Skipper alternatives →

Recent activity from authentik and Skipper

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 14h agoSkipperMove OIDC flow protection from Referer to cookies
  2. 14h agoSkipperv0.27.63: Store routes compressed-only, decompress on demand (#4198)
  3. 1d agoauthentikauthentik 2026.8 goes GA with Actors and domain-joined Agents
  4. 1d agoSkipperEskip predicates and filters accept negative numbers
  5. 1d agoSkipperFix token introspection handling
  6. 1d agoSkipperFix grant auth flow
  7. 1d agoSkipperUpdate outdated golang.org/x dependencies
  8. 9d agoauthentikauthentik 2026.8.0-rc7 lands Actors, enterprise Agents, and CAS sources
  9. 16d agoauthentik2026.8.0-rc6: flaky test and CI metadata fixes
  10. 16d agoauthentik2026.8.0-rc5: release plumbing only
  11. 16d agoauthentik2026.8.0-rc4: fix-only candidate
  12. 16d agoauthentik2026.8.0-rc3: cherry-picked fixes and CI work

Frequently asked questions

What is the difference between authentik and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. authentik 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.

Is authentik better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. authentik 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.

What are the best alternatives to authentik?

Top authentik alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "authentik alternatives" section above for the current picks, or visit /alternatives/authentik 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.