ESPHome
ESPHome adds a sixth 2026.10 beta, one more than 2026.9 needed before its .0.
A side-by-side editorial comparison of Grafana OnCall and incident.io — release velocity, themes, recent moves, and the top alternatives to consider.
Grafana OnCall's open-source line is in upkeep mode: runtime pins and Helm bumps, no features.
The last four releases of Grafana OnCall's open-source build contain no user-facing changes. Two Helm chart releases in mid-2025 were followed by v1.16.10 and v1.16.11 in early 2026, which pin Python 3.12.11, update urllib3, and adjust the Telegram integration's imports. The project still ships, but only to keep its dependencies current.
incident.io's Nexus agent now takes in your internal tools as well as going out to your editor.
Investigations, the agent that posts a root-cause hypothesis when an incident opens, is the center of incident.io; it went GA and then doubled its speed in September. Last week the company shipped a plugin that puts its agent skills into any coding harness. The newest release, Extensions, goes the other way: teams can feed Nexus their own debugging knowledge and connect internal or third-party tools to it.
The last four releases of Grafana OnCall's open-source build contain no user-facing changes. Two Helm chart releases in mid-2025 were followed by v1.16.10 and v1.16.11 in early 2026, which pin Python 3.12.11, update urllib3, and adjust the Telegram integration's imports. The project still ships, but only to keep its dependencies current.
The cadence is slowing: two releases in summer 2025, then a five-month gap, then two patch releases two weeks apart in early 2026. Nothing in these notes points to new alerting, scheduling, or escalation work in the open-source line.
Expect more v1.16.x patches for dependency and runtime hygiene, if any arrive at all; the entries give no sign of a 1.17 or a feature release.
Investigations, the agent that posts a root-cause hypothesis when an incident opens, is the center of incident.io; it went GA and then doubled its speed in September. Last week the company shipped a plugin that puts its agent skills into any coding harness. The newest release, Extensions, goes the other way: teams can feed Nexus their own debugging knowledge and connect internal or third-party tools to it.
incident.io is turning its agent into a two-way integration point. The plugin exports its skills into developers' agents, and Extensions imports a company's own tools and context into Nexus. Dashboards, ticket sync and alert routing keep incident.io as the record those skills read from and write to.
Expect worked examples or templates for common Extensions, such as internal deploy or feature-flag tools, and Investigations results that cite data pulled through them. The entries do not say how Extensions are built or whether they cost extra.
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 Grafana OnCall or incident.io.
ESPHome adds a sixth 2026.10 beta, one more than 2026.9 needed before its .0.
Semgrep adds Objective-C as an alpha target, its first new language since Dart went GA.
Currents opens every project on a health verdict: trend, state, and what to fix first.
CircleCI's V3 OIDC tokens bind cloud trust to where code and config came from.
Skipper patches its second filter advisory in a week, this one in the OPA request-body filter.
Cloudflare Tunnel ships 2026.10.2 five days after 2026.10.1, again with checksums only.
See all Grafana OnCall alternatives → · See all incident.io alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — incident response — within Infra & APIs. incident.io is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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. incident.io is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 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 Grafana OnCall alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Grafana OnCall alternatives" section above for the current picks, or visit /alternatives/grafana-oncall for the full list with editorial commentary on each.
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.