Knock
Knock plants its flag across every major AI platform: Claude, ChatGPT, Codex, and Cursor all get native connectors
A side-by-side editorial comparison of Authelia and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Authelia patches two access control bypass paths from canonicalization gaps.
Authelia v4.39.x is in a sustained hardening cycle: a critical security release in May fixed two authentication bypass paths, and subsequent patch releases have worked through a dense queue of OIDC protocol compliance bugs — resource indicators, client credentials foreign key handling, authentication strategy configuration, and resource strategy matching. The pace of micro-patches (v4.39.21 through v4.39.25 in a two-week window) reflects active production use surfacing edge cases.
werf v3.x dev channel drops CNI for netavark networking while the 2.x alpha track holds to bug fixes
werf maintains two active release channels: a 2.x alpha series (at v2.78.2) focused almost entirely on correctness backports — stapel panics, cache repo handling, import failures on symlinked paths — and a v3.x dev series pushing new capabilities. The v3.x track added authenticated secret values in deploy pipelines, renderPatches support, and a hard networking dependency switch in v3.4.0-dev.
Authelia v4.39.x is in a sustained hardening cycle: a critical security release in May fixed two authentication bypass paths, and subsequent patch releases have worked through a dense queue of OIDC protocol compliance bugs — resource indicators, client credentials foreign key handling, authentication strategy configuration, and resource strategy matching. The pace of micro-patches (v4.39.21 through v4.39.25 in a two-week window) reflects active production use surfacing edge cases.
The OIDC fix pattern is deliberate: Authelia is closing gaps in the parts of OAuth 2.0/OIDC that enterprise clients actually use — resource indicators, client credentials grants, pooled authentication. This isn't maintenance drift; it's building toward a more complete OIDC server for complex multi-client deployments. The access control canonicalization fix from May signals a broader audit of how Authelia normalizes domain names and usernames before authorization decisions.
The OIDC compliance fixes in v4.39.x are groundwork for new grant types and flows in a future major version. Expect device authorization flow or Pushed Authorization Requests (PAR) to appear in a v4.40 or v5.x roadmap entry once the protocol surface is cleaned up.
werf maintains two active release channels: a 2.x alpha series (at v2.78.2) focused almost entirely on correctness backports — stapel panics, cache repo handling, import failures on symlinked paths — and a v3.x dev series pushing new capabilities. The v3.x track added authenticated secret values in deploy pipelines, renderPatches support, and a hard networking dependency switch in v3.4.0-dev.
The v3.x dev channel is where werf's actual evolution happens: embedded Deno for deploy scripting (v3.2.0), the netavark networking switch (v3.4.0), and a systematic race-condition fix campaign across build, deploy, and registry layers. The 2.x alpha track functions as a backport target for correctness fixes, not a destination for new features. Registry-side cleanup reporting and Helm surface improvements in 3.x suggest the team is hardening the GitOps workflow layer before calling v3 stable.
The netavark switch in v3.4.0-dev is a hard breaking change — environments without netavark installed will lose rootless build capability. Expect migration documentation and a compatibility fallback discussion before any 3.x stable tag. The embedded Deno binary in 3.2.0 will likely gain more deploy scripting APIs once the networking layer stabilizes.
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 Authelia or werf.
Knock plants its flag across every major AI platform: Claude, ChatGPT, Codex, and Cursor all get native connectors
Honeybadger pivots from error tracker to full observability layer with AI-native query and anomaly detection
Resend expands from email API to full platform with SSO, analytics, and AI-native dev tooling
Helm 3 ships its final minor release while Helm 4.3 eliminates multi-minute status computation delays.
Quay ships a series of SSRF fixes in mirroring and proxy cache alongside steady CVE patching across 3.10 and 3.12 branches.
Redocly releases daily Reunite builds, hardening AI search RBAC and expanding MCP tool support.
See all Authelia alternatives → · See all werf alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Authelia 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Authelia 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.
Top Authelia alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Authelia alternatives" section above for the current picks, or visit /alternatives/authelia for the full list with editorial commentary on each.
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.