Vendor Status Dashboard

Monitor vendor status by region, prioritize critical dependencies, and triage incidents from a local Chrome Side Panel.

Is it you — or your vendor? Vendor Status Dashboard is a local-first vendor status monitor and SRE command center for answering that question under pressure — from a five-second toolbar scan to a persistent Chrome Side Panel. WHAT IT DOES - Monitor official public status feeds with global and in-scope truth kept visibly separate - Choose from 60 verified integrations across cloud, observability, CI/CD, payments, identity, communications, and developer platforms - Filter cloud incidents by region or exact component, without location access - Prioritize dependencies as P0, P1, or P2 and switch operational profiles - Group concurrent changes locally without claiming root cause - Acknowledge or snooze incidents in the popup and Side Panel; Pro adds the same actions in desktop alerts - Keep local notes and HTTPS runbook links beside the incident - Export/import a validated local configuration with secrets excluded - Toolbar badge counts vendors actually affected in your active scope FREE - Up to 5 enabled vendors from 60 built-in integrations and 15-minute checks - Regional/component relevance, criticality, Default profile, popup and Side Panel - Basic concurrent-change signal, one runbook, local onboarding, and safe backup PRO — $5/month or $39/year - Unlimited vendors (including custom Statuspage URLs) and named operational profiles - Faster checks down to 2 minutes - Desktop and Slack alerts with severity, criticality, quiet-hour and reminder rules - Advanced concurrent-change detail, multiple runbooks, and 30-day observed timeline PRIVACY No account. No tracking. No analytics. Everything runs locally in your browser. Operational profiles, notes, runbooks, triage, and exported configuration stay on your device. Network calls go only to status feeds you enable, your optional Slack webhook, and the license provider when you activate Pro. Full policy: vendorstatus.dev/privacy Built by an SRE who got paged too many times