DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of authentik and Knock — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | authentik | Knock |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | identity-provider, release-candidates, enterprise-agents, oauth2 | notifications, developer-infrastructure, rbac, workflow-automation |
| Last editorial update | 8d ago | 12h ago |
| Website | Visit → | — |
Seven release candidates in eight days, and rc7 quietly carries the endpoint agent.
authentik is deep in the 2026.8.0 release-candidate train — seven RCs, six of them fired on a single day in early August and rc7 a week later. Most of the train is CI plumbing, docs, and cherry-picked fixes, but rc7 is an order of magnitude larger and lands substantive work: an Actors primitive in core, an enterprise Agent that requires a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.
Knock is hardening for enterprise buyers while its agent takes over the analysis work.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
authentik is deep in the 2026.8.0 release-candidate train — seven RCs, six of them fired on a single day in early August and rc7 a week later. Most of the train is CI plumbing, docs, and cherry-picked fixes, but rc7 is an order of magnitude larger and lands substantive work: an Actors primitive in core, an enterprise Agent that requires a domain join and its own API scope, OAuth2 token exchange delegation, and a CAS source integration.
Two threads run through the branch. The identity surface keeps broadening at the protocol edge — CAS sources, WS-Fed, token exchange delegation, GitGuardian — while the enterprise tier grows an endpoint story with Agents and Actors, pushing authentik past browser-mediated SSO toward machine and device identity. The heavy CI investment across the RCs (test job split into ten, attestation and metadata fixes, release-branch validation) reads as release engineering being hardened ahead of a major.
2026.8.0 GA is the next step, and it is where the Agents and Actors work becomes a real story rather than a cherry-pick line. Expect the RC train to close out with fix-only candidates.
Knock ships weekly, in small, legible increments across three lanes: account governance (custom roles, passkeys), workflow primitives (wait-for-event, branch rebasing), and data ingress (Amplitude, Clay). The newest entry adds granular custom roles, which closes the last obvious gap in account-level access control. Alongside that, the in-product agent gained analytics, letting teams interrogate delivery performance without building reports.
Two arcs run in parallel. The infrastructure lane is buying enterprise credibility — roles, passkeys, audit-grade permissions — the checklist items that decide procurement rather than daily use. The data lane keeps widening what can trigger a workflow: product analytics from Amplitude, enriched rows from Clay, internal Slack channels as a destination. Together they push Knock from a notification API toward the messaging control plane, with the agent as the layer that explains what the plane did.
Expect the roles work to continue into audit logs or scoped API keys, since granular permissions without an activity trail is an incomplete enterprise story. More data sources are likely on the same cadence, with the CRM and warehouse categories the obvious remaining gaps.
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 Knock.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
See all authentik alternatives → · See all Knock alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Knock 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Knock 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.
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.
Top Knock alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Knock alternatives" section above for the current picks, or visit /alternatives/knock for the full list with editorial commentary on each.