authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Currents vs Skipper
A side-by-side editorial comparison of Currents and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Currents vs Skipper: at a glance
What is Currents?
Currents moved into the IDE and repriced itself around self-serve in the same fortnight.
Currents publishes short labeled changelog entries, and the visible window runs from April to August. Two carry real weight: a VS Code and Cursor extension bringing CI runs, failure triage and Playwright traces into the editor, and a pricing restructure a week later adding a self-serve Business plan, cheaper rates, revised overage and yearly usage pooling. Around them sit integration work with Linear and Slack, and a @currents/playwright 2.0 release supporting Playwright 1.60 and newer.
What is Skipper?
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.
Currents vs Skipper: editorial side-by-side
Currents
2.5INFRA · APIS
Currents moved into the IDE and repriced itself around self-serve in the same fortnight.
◆ Current state
Currents publishes short labeled changelog entries, and the visible window runs from April to August. Two carry real weight: a VS Code and Cursor extension bringing CI runs, failure triage and Playwright traces into the editor, and a pricing restructure a week later adding a self-serve Business plan, cheaper rates, revised overage and yearly usage pooling. Around them sit integration work with Linear and Slack, and a @currents/playwright 2.0 release supporting Playwright 1.60 and newer.
◆ Where it's heading
Currents is moving its surface toward where failures get fixed rather than where they get reported. The IDE extension, the Linear integration and the Slack notifications all describe the same handoff, and each one names agents alongside humans as the consumer. The pricing change points the same way commercially: a self-serve Business tier removes the sales conversation from the middle of the funnel, and that is precisely the tier an IDE extension is most likely to pull in.
◆ Prediction
Expect the agent-facing framing to become explicit, with the IDE extension and the API growing structured failure output a coding agent consumes directly rather than prose written for a human reader.
Skipper
6.3INFRA · APIS
Skipper tags a release per commit, so four versions in an hour can mean one real change.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Currents and Skipper
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 Currents or Skipper.
incident.io
Alert rate limits stop being per-source and start being per-tenant, by query.
Warp
The essay series keeps running ahead of the products it describes.
Node-RED
Both lines patch on the same day, and the reverted JSONata upgrade finally sticks.
werf
The 3.x line finally ships function: authenticated secret writes and render patches.
Infisical
Folder-level RBAC lands, and approvals finally get a webhook to talk to.
See all Currents alternatives → · See all Skipper alternatives →
Recent activity from Currents and Skipper
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoSkipperDependency: CodeQL scanning action bumped to 4.37.9
- 2d agoSkipperRoute formatting sheds redundant Sprintf calls: ~14% faster, ~16% fewer allocations
- 2d agoSkipperDependency: 15-package Go module group bump
- 2d agoSkipperAgent skill files renamed to match the specification
- 3d agoSkipperNew OIDC filter prunes oversized claim arrays before the cookie is written
- 6d agoSkipperValkey SetWithExpire becomes a single atomic command
- 28d agoCurrents[Improved] Better Slack notifications for CI test runs
- 1mo agoCurrents[Improved] New Pricing Plans ⚡
- 1mo agoCurrents[New] Currents IDE Extension ⚡
- 1mo agoCurrents[New] Integration with Linear
- 3mo agoCurrents[New] @currents/playwright 2.0 - Playwright 1.60+ Support
- 4mo agoCurrents[New] Invite guests without using paid seats
Frequently asked questions
What is the difference between Currents and Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Is Currents better than Skipper?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Skipper is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
What are the best alternatives to Currents?
Top Currents alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Currents alternatives" section above for the current picks, or visit /alternatives/currents-dev for the full list with editorial commentary on each.
What are the best alternatives to Skipper?
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.