authentik
The first patch on 2026.8 is twenty-odd fixes and no new surface.
Comparison · Infra & APIs
incident.io vs Oh Dear
A side-by-side editorial comparison of incident.io and Oh Dear — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ai-agents
incident.io vs Oh Dear: at a glance
What is incident.io?
Alert rate limits stop being per-source and start being per-tenant, by query.
Investigations went generally available on 5 August, with Nexus posting a root-cause hypothesis and its evidence into the incident channel minutes after declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before a rotation goes unstaffed, more filtering in Insights, agent-written status page updates, and a resource-by-resource Terraform provider rework. This release lets an alert source extract a value from the incoming payload with a query expression and shard its rate limit on that value, so one noisy customer or cluster no longer consumes the whole source's budget.
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.
incident.io vs Oh Dear: editorial side-by-side
incident.io
6.3INFRA · APIS
Alert rate limits stop being per-source and start being per-tenant, by query.
◆ Current state
Investigations went generally available on 5 August, with Nexus posting a root-cause hypothesis and its evidence into the incident channel minutes after declaration. The releases since have been the operational surround: a 24/7 schedule coverage policy that flags gaps before a rotation goes unstaffed, more filtering in Insights, agent-written status page updates, and a resource-by-resource Terraform provider rework. This release lets an alert source extract a value from the incoming payload with a query expression and shard its rate limit on that value, so one noisy customer or cluster no longer consumes the whole source's budget.
◆ Where it's heading
Two threads run in parallel. Nexus started inside the incident channel doing diagnosis and has moved outward to the customer-facing artifact. The second is platform work for customers running at scale — coverage policies, escalation routing, and now rate limiting that understands the shape of the payload rather than treating a source as one undifferentiated stream. Sharded limits are what you build when a single alert source fronts many tenants, which says something about the size of the deployments driving the roadmap.
◆ Prediction
Rate limits that read a query expression out of the payload share machinery with routing and deduplication, so the same expression surfacing in alert routing rules is the likely next step. The changelog entry does not say.
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.
Alternatives to incident.io and Oh Dear
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 incident.io or Oh Dear.
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.
Retool
Retool posts one-line changelog entries, and its agent work is the only visible thread
See all incident.io alternatives → · See all Oh Dear alternatives →
Recent activity from incident.io and Oh Dear
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoincident.ioShard alert source rate limits
- 4d agoOh DearMCP tools extended across maintenance, status pages and account management
- 8d agoincident.ioReworking our Terraform provider
- 11d agoOh DearAPI token scoping and MCP permission checks tightened
- 15d agoincident.ioAgent-written status updates, Pingdom metrics, and language self-serve
- 19d agoOh DearRecovery notifications restored after performance delta alerts
- 22d agoincident.io24/7 schedule coverage policy
- 25d agoOh DearJSON request bodies in HTTP checks; AI monitoring moves to the Laravel AI SDK
- 28d agoincident.ioInvestigations now available, powered by Nexus ⚡
- 29d agoincident.ioFlexible filtering in Insights
- 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 incident.io and Oh Dear?
Both compete on the same themes — ai-agents — within Infra & APIs. incident.io is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 incident.io better than Oh Dear?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. incident.io is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 incident.io?
Top incident.io alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "incident.io alternatives" section above for the current picks, or visit /alternatives/incident-io for the full list with editorial commentary on each.
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.