Skip to main content
Forge

Customer story · Cloud infrastructure

Incident context assembled before the responder joins

Meridian used Forge to gather the evidence an on-call engineer normally spends the first fifteen minutes collecting.

Meridian CloudGlobalParallel fan-outRetrievalSummarisationWebhooks
Faster time to mitigation
17 min
Incidents with an auto-brief
100%
Tools queried in parallel
6

The challenge

Every incident began the same way: an engineer paged awake, then twenty minutes of gathering deploy history, error rates, recent config changes and affected tenants from six different tools.

The approach

  1. 01

    Triggered a workflow on every page from the alerting system.

  2. 02

    Fanned out in parallel to collect deploys, metrics, config diffs and tenant impact.

  3. 03

    Summarised the collected evidence with explicit citations to each source.

  4. 04

    Posted the brief to the incident channel before the responder acknowledged the page.

The outcome

Responders open the channel to a structured brief instead of an empty thread. Time to mitigation dropped, and post-incident reviews start from a record that was captured automatically.

The brief is waiting when you open the laptop. That is fifteen minutes you get back at three in the morning.

Rowan IbarraPrincipal SRE, Meridian Cloud

More stories

Other demo teams using the platform

  • Northwind Logistics

    Exception handling that keeps a freight network moving

    Read story
  • Helios Bank

    Onboarding review with an evidence trail auditors accept

    Read story
  • Verdant Health

    Referral intake that never loses a document

    Read story

Get started

Start with one process, like they did

Every story here began with a single workflow that cost too much to run by hand.