incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
A side-by-side editorial comparison of authentik and WPML — release velocity, themes, recent moves, and the top alternatives to consider.
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.
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
The shipping 4.9 line is compatibility work: WordPress 7.1 support with a security hardening pass in the newest release, PHP 8.5 compatibility and a smoother site-migration flow before that, and WordPress 7.0's iframe-based block editor before that. The 5.0 beta running in parallel is the larger move — a redesigned interface, a simplified translation engine, and automatic translation switched on by default for new sites.
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.
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.
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.
The shipping 4.9 line is compatibility work: WordPress 7.1 support with a security hardening pass in the newest release, PHP 8.5 compatibility and a smoother site-migration flow before that, and WordPress 7.0's iframe-based block editor before that. The 5.0 beta running in parallel is the larger move — a redesigned interface, a simplified translation engine, and automatic translation switched on by default for new sites.
Two clocks again. The maintenance clock is dictated entirely by other people's releases: WordPress majors, PHP versions, Divi 5, Elementor. Enough of this feed is compatibility that it reads as the real cost of being a translation layer inside someone else's ecosystem. The product clock points one direction, toward automation — cost and time estimates before sending content, one-click recovery for stuck jobs, automatic detection of custom Elementor widgets, and now automatic translation as the starting state rather than an option. The 4.9.7 security hardening is worth noting alongside a beta in flight: the stable line still gets real attention.
Expect the 5.0 line to move from beta to production with the automatic-first defaults intact, followed by continued compatibility maintenance as WordPress core and major builders evolve.
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 WPML.
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.
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all authentik alternatives → · See all WPML alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. authentik and WPML 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. authentik and WPML 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.
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 WPML alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "WPML alternatives" section above for the current picks, or visit /alternatives/wpml for the full list with editorial commentary on each.