← Back to home
Comparison · Infra & APIs

authentik vs Mergify

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

authentik vs Mergify: at a glance

FeatureauthentikMergify
SectorInfra & APIsInfra & APIs
Velocity score6.36.3
Sparks · 30d11
Top themesidentity, sso, outposts, proxymerge-queue, ci-automation, github, stacked-prs
Last editorial update20h ago5d ago
WebsiteVisit →Visit →

What is authentik?

The first patch on 2026.8 is twenty-odd fixes and no new surface.

2026.8.1 is the first patch after the 2026.8 release, and the GitHub tag carries only a link to the docs. The fix list behind it is entirely correctness work: proxy outposts no longer break header parsing in non-compliant backends or double-send the host on token introspection, X-Forwarded-For now takes the rightmost untrusted IP, expression policies stop polluting the request context, and websocket subprotocol negotiation is relayed properly. New installs get a one-day default token duration. Nothing here changes what authentik can do.

Read the full authentik trajectory →

What is Mergify?

Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.

Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.

Read the full Mergify trajectory →

authentik vs Mergify: editorial side-by-side

A
authentik
INFRA · APIS
6.3

The first patch on 2026.8 is twenty-odd fixes and no new surface.

◆ Current state

2026.8.1 is the first patch after the 2026.8 release, and the GitHub tag carries only a link to the docs. The fix list behind it is entirely correctness work: proxy outposts no longer break header parsing in non-compliant backends or double-send the host on token introspection, X-Forwarded-For now takes the rightmost untrusted IP, expression policies stop polluting the request context, and websocket subprotocol negotiation is relayed properly. New installs get a one-day default token duration. Nothing here changes what authentik can do.

◆ Where it's heading

The release train is behaving as expected after a major: 2026.8.0 landed in mid-August after a long rc series, and the first patch is dominated by outpost and proxy edge cases, which is where authentik meets other people's infrastructure and therefore where the reports come from. The security-adjacent items — X-Forwarded-For parsing, expression context isolation, a shorter default token life — are hardening rather than capability.

◆ Prediction

Patch releases on a fresh major usually run in a short series, so a 2026.8.2 with the remaining outpost reports is the likely next entry. The tag body links to docs rather than describing anything, so nothing further is stated.

M
Mergify
INFRA · APIS
6.3

Mergify's queue learned to merge stacked pull requests, then spent August tightening the edges.

◆ Current state

Mergify automates merge queues for GitHub, and August was a mix of one real capability and a batch of contract cleanup. The queue can now merge GitHub-native stacked pull requests in order, speculative-check budgets apply per lane across dynamic scope sets, and conditions can match on whether a pull request came from a fork. Alongside that, the badge API was removed, pagination stopped advertising first and last links, and author-run commands were restricted to fork pull requests by default.

◆ Where it's heading

Two threads. The queue is absorbing workflows that used to sit outside it - stacked pull requests, flaky-test detection and rerunning within a CI budget - which pushes Mergify from a merge gate toward owning the whole pre-merge pipeline. The other thread is a deliberate narrowing of surface: deprecated endpoints removed, the github_actions action marked for removal in March 2027, default command permissions tightened around forks. That is a product trimming what it maintains so the queue can take on more.

◆ Prediction

Expect more of the pre-merge pipeline to move inside the queue on the flaky-test pattern, and further deprecations of automation that overlaps with what GitHub Actions now does natively.

Alternatives to authentik and Mergify

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 Mergify.

See all authentik alternatives → · See all Mergify alternatives →

Recent activity from authentik and Mergify

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

  1. 1d agoauthentik2026.8.1 patches proxy outposts, header parsing, and expressions
  2. 8d agoMergifyPer-lane check capacity for dynamic scopes
  3. 8d agoMergifyPagination drops the first and last links
  4. 8d agoMergifyRepository badge API removed
  5. 8d agoMergifyClearer reason when the merge queue can't create the draft pull request
  6. 14d agoauthentikauthentik 2026.8 goes GA with Actors and domain-joined Agents
  7. 21d agoMergifyMerge GitHub stacked pull requests with the merge queue
  8. 22d agoMergifyNew from-fork condition attribute
  9. 22d agoauthentikauthentik 2026.8.0-rc7 lands Actors, enterprise Agents, and CAS sources
  10. 29d agoauthentik2026.8.0-rc6: flaky test and CI metadata fixes
  11. 1mo agoauthentik2026.8.0-rc5: release plumbing only
  12. 1mo agoauthentik2026.8.0-rc4: fix-only candidate

Frequently asked questions

What is the difference between authentik and Mergify?

They serve adjacent needs but don't currently overlap on shipped themes. authentik and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 authentik better than Mergify?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. authentik and Mergify are shipping at a similar cadence (velocity 6.3 vs 6.3, 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 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 Mergify?

Top Mergify alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Mergify alternatives" section above for the current picks, or visit /alternatives/mergify for the full list with editorial commentary on each.