// no-signup product demo
A real incident from a real storefront we run and break on purpose. It shows the incident-response experience without credentials, signup, or a live customer system.
now · active incident
Stripe webhook signature verification has failed on every delivery since 14:02. Payments are succeeding; nothing is being fulfilled.
Stripe dashboard → webhook endpoint → recent deliveries.
now
7 services watching on form-01 · all quiet · checked just now.
Our own demonstration store, not a customer. See how the decision works →
Both panels above are a real Beaam alert format, not a screenshot of a dashboard. Five fixed fields — what service, what triggered, how long, what it correlates with, where to look — sized to be understood on a phone at 3am without opening anything.
The second panel matters as much as the first. "All quiet" is a message Beaam sends on purpose, every day, because silence you cannot verify is indistinguishable from a monitor that has died.
// the same incident, end to end
The alert above is not a mock-up of nothing. It comes from Form/01 by Soft Theory — a working storefront Beaam watches the way it would watch yours. Below is the whole loop: what customers saw, what Beaam sent, and what it took to fix.
demonstration store, not a customer. Built by us, monitored by us, and broken deliberately so this page can show you something true. Form/01 is not for sale and nobody is charged.
01 — the storefront
A limited run at $29. Someone clicks buy, the unit is held, Stripe takes the payment. On a good day the file arrives by email about four seconds later.
02 — what actually happened at 14:02
The webhook signing secret was rotated and never updated in Drop.
Every surface still looked healthy. The storefront rendered, the payment page loaded, Stripe reported success and charged the card. The only thing that stopped was the part nobody watches — and every purchase since 14:02 took payment and delivered nothing.
This is the failure class Beaam exists for. There is no error page to see, no 500 in a log, and no customer complaint for another twenty minutes. A status check would have reported everything fine.
03 — 8 minutes later
Stripe webhook signatures failing for 8 min. Buyers are paying and getting an error. Start here: Stripe dashboard → webhook endpoint.
Not "an anomaly was detected". The service, the symptom, how long, what it costs, and the one screen to open — the same five fields as the panel at the top of this page, because it is the same format.
04 — the recovery
Updating the signing secret fixed deliveries going forward. The purchases already taken were not lost: each one sat in a retry queue that had backed off rather than given up, and the creator resent the ones that had stopped trying. Buyers got their file. Nobody had to reconcile a spreadsheet.
The recovery matters as much as the alert. Knowing quickly is only useful if the damage is still reversible when you find out.
Drop is open source — read exactly what it does, including how it fails.
Honest limits: the incident is real and so is the application, but the timings on this page are staged rather than measured, and Drop is ours — a store we built and break deliberately, not a customer. It proves nothing about anyone else’s stack, and nothing here should be read as a usage figure or a reference. What it demonstrates is the shape of what arrives: the deliberate absence of a graph, a severity taxonomy, or a link to a dashboard you would have to interpret.
The parts that genuinely need your own stack are the ones worth testing for real: whether the defaults are right for your services, and whether the alert lands on your phone. Both take about five minutes on the free plan, which includes sending a real test alert through your own channel.
Free includes two integrations, five watched services, and email alerts.
Start free →