authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Doppler vs Skipper
A side-by-side editorial comparison of Doppler and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Doppler vs Skipper: at a glance
What is Doppler?
Doppler shipped an on-prem build — the secrets manager that only ran as SaaS now runs in your datacenter.
Monthly digests, each one a list, and the captured bodies cut off partway so only the opening items are legible. June leads with Doppler On-prem, alongside role filters on the dashboard, warnings that show downstream impact before deleting inherited or referenced data, and fuzzy matching in secret search. The months before it are steady platform work: Integration Access Scoping via API and Terraform, the ability to redact every historical version of a secret so deleted history is genuinely gone, Azure Service Principal rotated and dynamic secrets, activity-log forwarding to multiple destinations per service type including AWS SQS, and CLI token creation from the MCP server.
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.
Doppler vs Skipper: editorial side-by-side
Doppler
0.0INFRA · APIS
Doppler shipped an on-prem build — the secrets manager that only ran as SaaS now runs in your datacenter.
◆ Current state
Monthly digests, each one a list, and the captured bodies cut off partway so only the opening items are legible. June leads with Doppler On-prem, alongside role filters on the dashboard, warnings that show downstream impact before deleting inherited or referenced data, and fuzzy matching in secret search. The months before it are steady platform work: Integration Access Scoping via API and Terraform, the ability to redact every historical version of a secret so deleted history is genuinely gone, Azure Service Principal rotated and dynamic secrets, activity-log forwarding to multiple destinations per service type including AWS SQS, and CLI token creation from the MCP server.
◆ Where it's heading
Two commitments run through this window. The first is that everything must be reachable programmatically — API and Terraform coverage for access scoping, Change Requests endpoints in the v3 API, service account identity management, MCP-driven CLI authentication. The second is control over the secret's whole lifecycle rather than its current value: rotation, dynamic generation, history redaction, and delete-time impact warnings all treat a secret as something with a past and dependents. On-prem is what those two make sellable to the customers who could not use Doppler at all.
◆ Prediction
Expect the on-prem build to drive the next stretch of work — parity gaps, upgrade paths, and air-gapped handling of the integrations that currently assume outbound access. The truncated digests make anything finer than that unreadable from the feed.
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 Doppler 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 Doppler 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 Doppler alternatives → · See all Skipper alternatives →
Recent activity from Doppler 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
- 2mo agoDopplerDoppler On-prem released ⚡
- 3mo agoDopplerTerraform support for access scoping and full secret-history redaction
- 4mo agoDopplerMultiple activity-log forwarding destinations and AWS SQS support
- 5mo agoDopplerAzure Service Principal rotated and dynamic secrets
- 6mo agoDopplerCLI token creation from the MCP server, with attribution in logs
- 7mo agoDopplerAWS Secrets Manager multi-secret sync loses its 64KiB limit
Frequently asked questions
What is the difference between Doppler and Skipper?
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.
Is Doppler 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 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.
What are the best alternatives to Doppler?
Top Doppler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Doppler alternatives" section above for the current picks, or visit /alternatives/doppler 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.