Skip to content

A real check, recorded

Stripe said they were paying. The app locked them out.

This is a recorded check, not an illustration: DROP OS's own sample app, on staging, with a Stripe test-mode subscription. We broke it on purpose on 25 September 2026 to show exactly what you would see. No real customer was involved.

What each system reported for the same test customer
SystemQuestionAnswer
StripeSubscription activeYes
Your app's recordsPlan active for this accountYes
A real signed-in browserReached the paid pageNo

The fault we committed, exactly as deployed (sample commit c08800a):

const FAULT_UNTIL=Date.parse('2026-09-25T21:15:00Z');
const entitled=account?.lifecycle==='active'&&await auth.entitlement(session.access);
const allowed=entitled&&!(Date.now()<FAULT_UNTIL);

It switched itself off at 21:15 UTC in case we forgot to revert it. We reverted it at 20:30.

20:27:38

The bad deploy

A deliberate fault in the protected page's access check stopped letting paying customers in. Stripe still showed the subscription active. The app's own records still said the customer had a plan.

20:28:04

The deployment started a check

The deployment finished, and the workflow in the repository began a check on its own. Nobody pressed a button.

20:28:40

A mismatch — held, not reported

The signed-in browser could not reach the paid page. Payment and access updates can arrive seconds apart, so DROP OS gave the systems 15 seconds to agree before calling it a fault.

20:29:21

Still wrong, so reported

The systems still disagreed after the window. Verdict: CONTRADICTION.

20:29:22

Incident alert

The incident email to the workspace owner was handed to our email provider — 1 minute 44 seconds after the bad deploy.

20:30:58

Fixed, and confirmed

The line was reverted and deployed. The next check passed, and the recovery email followed a second later.

It shows the whole path working on a real deployment: GitHub, the published workflow, Stripe, a Supabase entitlement function, a headless browser signed in as a dedicated test customer, and DROP OS's server deciding the verdict from what was observed.

It is one check of one access promise on one sample app. It does not prove every customer or feature works, and on your app it needs a dedicated test customer and a staging environment. The trial shows the verdict and which system disagreed; the evidence, investigation steps and email alerts are on the paid plan.

Run the same check on your staging app.

3 days and 10 completed checks, no card.