ImpactRelay
For small SaaS teams with critical vendors

Know what the outage actually breaks.

ImpactRelay maps Stripe, AWS, OpenAI, and other vendor incidents to your product features—then posts an evidence-backed impact brief to Slack.

Explore the live demo
20-minute assisted setup No source-code access Pilot credited to first month
Vendor signal
# incidents Live demo
ImpactRelayAPPnow
Impact detectedhigh confidence

Elevated errors creating Checkout Sessions

Stripe Checkout is connected to 1 mapped product feature.

Affected
  • Customer checkout
No mapped impact
  • AI brief generation
  • Invoice exports
Source Stripe StatusComponent CheckoutDetected 2 minutes ago
Your product impact
Impact, not another alert.
STRIPEAWSOPENAIVERCELCLOUDFLARE
The missing layer

Status pages tell you what happened to them.

You still have to work out what it means for your customers. ImpactRelay keeps that knowledge ready before the next incident.

Without ImpactRelay

Alert first. Investigate from scratch.

  1. 0:00 Generic vendor alert lands
  2. 0:05 Search docs and ask engineering
  3. 0:18 Support asks what to tell customers
  4. ×0:24 First credible answer
With ImpactRelay

Signal in. Product impact out.

  1. 0:00 Vendor component detected
  2. 0:01 Dependency map checked
  3. 0:02 Evidence and confidence attached
  4. 0:02 Team knows what is affected
One narrow workflow

From outside signal to inside truth.

No new observability stack. Just the context your existing alert is missing.

01

Map dependencies

Connect customer-facing features to the exact vendor components they rely on.

02

Interpret the signal

Match each vendor incident against reviewed mappings, not an ungrounded AI guess.

03

Brief the team

Post affected and unaffected features, evidence, timing, and confidence to Slack.

Designed for trust

Certainty where possible. Honesty where it isn’t.

ImpactRelay does not hide uncertainty behind polished prose. Every conclusion carries its evidence and confidence.

  • Vendor and component source shown
  • Customer-reviewed dependency mapping
  • Explicit low-confidence fallback
  • Human correction captured for next time
Assessment tracehigh confidence
Vendor incidentStripe
Affected componentCheckout
Reviewed mappingCheckout → Customer checkout
Product impactCustomer checkout affected
Founding pilot

Prove the signal before you subscribe.

A hands-on 30-day pilot for one product. If it earns a permanent place in your incident workflow, continue monthly.

30-day assisted pilot
$49
100% credited
  • One SaaS product
  • Up to 10 critical vendors
  • Up to 25 feature mappings
  • One Slack workspace
  • Assisted 20-minute setup
  • Three incident simulations

Then $99/month only if you continue. The pilot payment becomes your first-month credit.

Questions, answered

Before you map your first dependency.

Need a detail not covered here? Ask directly.

Is this another uptime monitor?

No. ImpactRelay consumes vendor incident signals and translates them through your dependency map. The output is which product features are affected, not another generic downtime notification.

Which vendors are included in the pilot?

The assisted pilot supports up to 10 critical vendors. The initial catalog includes Stripe, AWS, Cloudflare, GitHub, OpenAI, Anthropic, Clerk, Supabase, Vercel, and SendGrid.

How long does setup take?

We map your first product with you in a 20-minute session. You identify the features customers care about; we connect them to the relevant vendor components.

How do you avoid false impact alerts?

Every assessment cites the vendor component, source, mapping, and confidence level. Uncertain mappings are labeled for confirmation instead of presented as facts.

What happens after the 30-day pilot?

If the product saves meaningful triage time, continue on the $99/month founding plan. Your $49 pilot payment is credited to the first month. If it does not help, stop there.

Do you need access to our source code?

No. The pilot uses a lightweight dependency map containing feature names, vendor names, and vendor components. It does not require repository or production access.

The next outage is already scheduled. You just don’t know when.

Know the impact before the questions arrive.