LoginSign Up
← Back to all sparks
I

incident.io

INFRA · APIS
Velocity5.0

Incident management, on-call, and status page platform for engineering teams

incident.io ↗

incident.io closes the alert-to-ticket loop with bidirectional sync and tightens on-call infrastructure.

devtoolsalertingincident-managementai-opsterraformon-call
◆Current state
incident.io is shipping at a consistent pace across alert pipeline hardening, on-call workflow completeness, and integration depth. The most significant recent addition was Investigations GA (powered by Nexus) in early August — AI-generated root cause hypotheses with supporting evidence posted to the incident channel within minutes of declaration. The six most recent releases focus on operational correctness: bidirectional ticket sync, alert source team assignment, rate limit sharding, Terraform provider rework, and 24/7 schedule coverage policies.
◆Where it's heading
The product is building toward a complete incident lifecycle platform — alert ingestion through triage, response, and root cause analysis — with AI (Nexus/Investigations) handling the diagnostic layer and integrations (ITSM, Terraform, Pingdom) filling the operational completeness gaps. Bidirectional ticket sync closes a long-standing friction point with ITSM workflows. The Terraform provider rework is a deliberate investment in enterprise adoption through infra-as-code, signaling a bet that platform-engineering teams define enterprise retention.
◆Prediction
The Terraform provider rework, once complete resource-by-resource, will unlock platform-engineering teams who need reproducible incident infrastructure. Nexus/Investigations will likely expand into proactive anomaly detection — flagging potential incidents before a human declares them.

◆Recent moves

  1. 1d ago

    Bidirectional sync for incident tickets

    Bidirectional ticket sync closes the loop between incident channels and ITSM systems: ticket state changes now propagate back into the incident, eliminating the manual sync that had made tickets a read-only mirror. For enterprises where ITSM approval workflows control incident closure, this is a meaningful correctness improvement rather than a convenience feature.

    View source ↗
  2. 13d ago

    Easier alert source set-up

    Assigning an alert source to a team without payload-matching removes a configuration friction point that blocked small or quickly-evolving teams from routing alerts correctly. It simplifies a step that previously required understanding payload schemas before getting any alerts flowing.

    View source ↗
  3. 15d ago

    Shard alert source rate limits

    Rate limit sharding by extracted payload value — customer ID, region, or similar — lets high-volume alert sources burst selectively rather than globally throttling the source. For teams with multi-tenant alerting pipelines, this prevents one noisy customer from blocking alerts from others.

    View source ↗
  4. 22d ago

    Reworking our Terraform provider

    A resource-by-resource Terraform rework signals investment in infra-as-code as a first-class adoption path — not an afterthought. Enterprise platform teams who provision incident infrastructure via Terraform will get more maintainable, predictable configs; the ongoing commitment is itself a meaningful signal about where the product is heading.

    View source ↗
  5. 29d ago

    A few improvements to Status Pages

    Agent-triggered status page updates, Pingdom uptime metric integration, and self-serve language selection are each gap-filling additions for teams running public status pages. Agent-triggered updates in particular fit the Nexus automation arc — reducing manual steps during a live incident.

    View source ↗
  6. 1mo ago

    24/7 schedule coverage policy

    A coverage policy that flags schedule gaps ensures no alert window goes unmonitored — addressing a real operational risk for organizations running complex, multi-timezone on-call rotations. This is correctness infrastructure rather than UI polish: a misconfigured schedule without coverage gaps can mean missed incidents.

    View source ↗