authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
Oh Dear vs Skipper
A side-by-side editorial comparison of Oh Dear and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Oh Dear vs Skipper: at a glance
What is Oh Dear?
The monitoring account is becoming something an agent operates, not just a dashboard someone reads.
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
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.
Oh Dear vs Skipper: editorial side-by-side
Oh Dear
5.0INFRA · APIS
The monitoring account is becoming something an agent operates, not just a dashboard someone reads.
◆ Current state
Oh Dear is an uptime and site-health monitoring service shipping a dated changelog most weeks, with each release mixing new capability, security work and fixes. The MCP server is the thread running through all of it: monitor create, update and delete arrived in May, tag groups and notification routing in June, and the August release extends it across downtime, check summaries, domain intelligence, maintenance windows, check state, status page updates, notification destinations, scheduled tasks, Broken Links, Application Health and account management. Around that sit steady monitoring improvements — consecutive-failure thresholds for sitemap alerts, raw JSON bodies in HTTP checks, better handling of out-of-order scheduled-task pings.
◆ Where it's heading
Two things are being built at once and they depend on each other. The MCP surface keeps widening until an assistant can run the account end to end, and the authorization model keeps being tightened to make that safe — API token scoping, permission checks on monitor-modifying tools, access controls on the new write tools, sessions invalidated on password change. Each release moves both. Underneath, the business plumbing is being tidied in public too: legacy pricing shown on the plan chooser, corrected affiliate terms, an agency-focused pricing structure, AI wizard placeholder monitors excluded from usage limits.
◆ Prediction
Expect the MCP tool surface to keep filling in the remaining corners of the product and the permission model to keep pace with it, and expect the November Slack connection deprecation already being warned about in-app to produce a migration release before then.
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 Oh Dear 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 Oh Dear 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 Oh Dear alternatives → · See all Skipper alternatives →
Recent activity from Oh Dear 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
- 4d agoOh DearMCP tools extended across maintenance, status pages and account management
- 6d agoSkipperValkey SetWithExpire becomes a single atomic command
- 11d agoOh DearAPI token scoping and MCP permission checks tightened
- 19d agoOh DearRecovery notifications restored after performance delta alerts
- 25d agoOh DearJSON request bodies in HTTP checks; AI monitoring moves to the Laravel AI SDK
- 1mo agoOh DearApplication Health metadata limit doubled; scheduled-task ping fixes
- 1mo agoOh DearAgency pricing introduced; Forge import moves to scoped API v2 tokens
Frequently asked questions
What is the difference between Oh Dear and Skipper?
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 6.3 vs 5.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 Oh Dear 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 5.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 Oh Dear?
Top Oh Dear alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Oh Dear alternatives" section above for the current picks, or visit /alternatives/ohdear 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.