LoginSign Up
← Back to all sparks
S

Spike

COMMS
Velocity0.0

Spike grinds out incident-management ergonomics — number-comparison alerts, more integrations, broader AWS auto-resolution.

incident managementon-callalertingintegrationsdevopsoperator ergonomics
◆Current state
Spike is an incident management and on-call platform competing in PagerDuty's category. The recent quarter's releases are uniformly incremental — numeric comparison operators in Alert Rules, broader AWS auto-resolution coverage (now including SNS), Jenkins and NinjaOne integrations, an inbound Jira trigger, day-of-week alert routing, admin-managed Out of Office. Each release shaves friction from a specific operator workflow without changing what Spike fundamentally is.
◆Where it's heading
Spike's competitive strategy reads as 'be more methodical about the long tail of operator paper-cuts.' The integration cadence is high — Jenkins, NinjaOne, Jira inbound, calendar links — the alert rule grammar keeps expanding (comparison operators, day-of-week conditions), and the on-call surface keeps gaining flexibility (gaps, scheduled layers, admin-managed OOO). No directional moves, but very consistent incremental velocity.
◆Prediction
Expect more integration additions in the same vein (CI/CD tools, IT monitoring vendors), continued alert rule grammar expansion (time-of-day conditions and frequency-based thresholds are the obvious next axes), and more team-management features around on-call rotations.

◆Recent moves

  1. 4mo ago

    Compare numbers in Alert Rules

    Numeric comparison operators in Alert Rules unlock value-based routing — set P1 if CPU > 80, escalate if SSL expiry days < 3. Concrete operator-friction relief for teams that previously needed external automation to do this.

    View source ↗
  2. 4mo ago

    Better AWS auto-resolution

    AWS auto-resolution now covers SNS incidents — small-looking but operationally meaningful, since stale auto-recoverable incidents are a major contributor to alert fatigue.

    View source ↗
  3. 6mo ago

    Admins can now manage Out of Office for the team

    Letting admins set Out of Office for any team member fixes a coverage-planning gap that previously required users to set their own OOO — and the team-wide visibility it adds is the more meaningful change for rotation planning.

    View source ↗
  4. 6mo ago

    Jenkins integration for CI/CD alerts

    Jenkins integration adds CI/CD pipeline alerts to Spike — squarely on the integration-coverage trajectory, makes Spike more tenable as the single alerting destination for DevOps teams.

    View source ↗
  5. 6mo ago

    Route alerts by day of the week

    Day-of-week routing in Alert Rules — phone calls on weekend traffic spikes, Slack-only on quiet Mondays. Practical extension of the rule grammar that addresses a common manual-workaround pattern.

    View source ↗
  6. 6mo ago

    New Integrations → NinjaOne and Jira Inbound

    NinjaOne lands as a new IT-infrastructure source and Jira gains an inbound trigger — both extend Spike's reach into adjacent ops tooling, the Jira inbound in particular bridging dev and on-call workflows that previously needed manual escalation.

    View source ↗