01Every deployment starts a real access check
Once connected, DROP OS follows your approved release trigger automatically. The check stays tied to the repository and exact code that shipped.
- One-time installation
- Automatic deployment trigger
- Exact release history
02Three systems become one customer signal
For your configured test customer, DROP OS compares the Stripe subscription, the access your app grants in Supabase, and the protected page reached after login.
- Stripe payment state
- Supabase entitlement state
- Real signed-in browser path
03Allow time for updates to settle
Payment and access updates can arrive at different times. DROP OS rechecks within a 15-second settling window before reporting a lasting mismatch.
- Time for updates to settle
- Pending result while checking
- Persistent mismatch detection
04Know what to investigate
See which systems disagreed and what the test customer experienced. The paid plan adds supporting evidence, investigation steps and an email to the workspace owner.
- Failure localisation
- Clear repair guidance
- Evidence on demand
05Recovery closes the loop
A corrected follow-up preserves the incident history and confirms that payment, entitlement and access agree again.
- Verified follow-up
- Auditable recovery
- Unchanged history
06Manage your plan and check allowance
See your remaining checks in the dashboard. Start a subscription or manage cancellation from the billing page.
- Check allowance
- Subscription management
- Cancellation in the billing portal