authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
A side-by-side editorial comparison of Intigriti and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
A bug bounty platform grinding down the friction in triage rather than chasing new surface.
Intigriti runs crowdsourced security testing, and the tracked window from March to May 2026 is entirely operational refinement of the program side. Insights gained triage metrics covering review status, decision alignment and time to first assignment, plus time grouping by week, quarter or year. Submission handling picked up self-service unassignment so work can move between triagers. Asset management gained predefined sorting and a sort that surfaces AI skill suggestions awaiting review. The most recent entry adds a possible-bounty variable to message templates so payout estimates populate themselves. The feed has published nothing since 6 May 2026.
Skipper tags a release per commit, so four versions in an hour can mean one real change.
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
Intigriti runs crowdsourced security testing, and the tracked window from March to May 2026 is entirely operational refinement of the program side. Insights gained triage metrics covering review status, decision alignment and time to first assignment, plus time grouping by week, quarter or year. Submission handling picked up self-service unassignment so work can move between triagers. Asset management gained predefined sorting and a sort that surfaces AI skill suggestions awaiting review. The most recent entry adds a possible-bounty variable to message templates so payout estimates populate themselves. The feed has published nothing since 6 May 2026.
The work is aimed squarely at the customers with large programs, where the bottleneck is not finding researchers but processing what they send. Every entry in the window reduces manual handling somewhere in that pipeline: sorting large asset inventories, keeping the submission queue unblocked, measuring whether triage decisions are consistent, and removing copy-paste from researcher communication. The AI thread is deliberately modest — suggestions for required asset skills that a human reviews and applies, never applied automatically.
The four-month gap in this feed makes a confident prediction unwise; on the evidence here the natural next step is measuring the payout side with the same Insights treatment triage received, but nothing in the entries confirms it is being built.
Skipper is Zalando HTTP router and reverse proxy, and it cuts a version tag for essentially every merged commit. Four tags landed inside one hour on 31 August: three dependency and housekeeping commits and one real optimisation that removed redundant Sprintf calls from route formatting, measured at roughly 14 percent faster route serialisation and 16 percent fewer allocations. The releases before them are the same mix, with the OIDC claim-pruning filter and the atomic Valkey SetWithExpire as the recent capability work.
Two kinds of change alternate on this feed: filter and backend capability arriving occasionally, and a continuous stream of dependency group bumps between them. The capability side has been concentrated on the proxy edge — OIDC claim handling, load-balancer algorithms, Valkey-backed state — while the performance work targets the route data path itself. Because the tagging is per commit, cadence here says nothing about how much shipped.
Given the benchmark-driven optimisation in this batch, further allocation work on the eskip formatting and routing path is the most likely next capability change, with dependency bumps continuing to fill the tags between.
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 Intigriti or Skipper.
The first patch on 2026.8 is twenty-odd fixes and no new surface.
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.
See all Intigriti alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 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. Skipper is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 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 Intigriti alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Intigriti alternatives" section above for the current picks, or visit /alternatives/intigriti for the full list with editorial commentary on each.
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.