This is a real, unedited run of MultiGuard — no mockups, no cherry-picking. It's the store's whole promise: see the tool do the job before you pay for it.
demo · MultiGuard · 2026-09-07
Live run — Saturday 07:42, duplicate refunds firing
Trigger: Stripe webhook replay after a provider outage. Your refund-sync connector starts re-processing yesterday's queue.
MultiGuard dashboard, single pane:
▸ shopify-order-sync — ACTIVE — 214 writes/hr (baseline 30) ⚠ ▸ stripe-refund-relay — ACTIVE — 41 writes/hr (baseline 4) ⚠ ▸ sheets-revenue-rollup — ACTIVE — nominal ▸ slack-alerts-bot — ACTIVE — nominal ▸ hubspot-contact-push — UNREACHABLE — last seen 07:31 ⚠
Four of five writes stopped in 11 seconds. One is honestly reported as unknown so you go handle it directly instead of finding out Monday.
You fix the webhook filter, hit RESUME on the two Stripe-side connectors, leave the rest frozen. Local log records who froze what and when.
Where this stops:
MultiGuard flips connectors that expose a pause or read-only control. It cannot revoke OAuth tokens, and it cannot undo the 63 duplicate refunds already written before 07:43 — that's a reconciliation job on your side.
It also can't act on a connector it can't reach, as above. It tells you clearly instead of guessing. What it buys you is the eleven seconds instead of five dashboards and a login prompt.