Skip to content

Questions, answered

Questions about setup and checks.

Understand what a check covers, how alerts work and what to prepare before connecting your application.

What does DROP OS monitor?

One configured test customer’s Stripe subscription, the access your app grants in Supabase, and the protected journey reached after login. It does not check every customer or feature, or monitor between deployments.

When does a check run?

After the one-time setup, the generated GitHub workflow starts automatically when the approved deployment succeeds. A manual trigger remains available for diagnosis.

Is this another uptime monitor?

No. Uptime can say every service responds while a paying customer remains locked out. DROP OS checks whether the systems agree on that customer’s access.

Will normal webhook delay create false alarms?

DROP OS allows time for payment and access updates to settle, with repeat checks within a 15-second settling window. It reports a lasting mismatch as an incident and incomplete evidence as an unverified result.

What happens when access breaks?

The dashboard shows where the subscription, app access setting and browser journey disagree. The paid plan adds evidence and investigation steps. Your team repairs the issue; a later check confirms recovery.

Do I paste Stripe or database secrets into DROP OS?

No. Provider credentials stay in your protected GitHub environment. DROP OS receives narrow status facts, not card data, database passwords or customer records.

Does DROP OS send incident emails?

On the paid plan, the workspace owner receives incident and recovery emails. DROP OS retries failed email delivery within a limit, and delivery status is visible in the dashboard. Email alerts are not included in the trial.

Can I delete my data?

Yes. Project and workspace deletion are owner-scoped and retry-safe. Permanent account deletion requires your current password and an explicit confirmation phrase.

Where does DROP OS itself run?

On a dedicated application and domain of its own, with an isolated schema and row-level tenant isolation inside our production Supabase project in London. The application you connect stays yours: the check runs inside your own GitHub account and submits narrow facts to us, so we never hold your provider credentials.

Is DROP OS ready for production customer data?

Yes, and the reason is narrower than it sounds — DROP OS never receives your customer records. The check runs inside your own GitHub account against one test customer you nominate, and submits narrow facts and digests rather than data. A trial is limited to a staging application of yours, without a card. A paid subscription is open, and unlocks checks against your live application. What is still unsettled is commercial rather than technical. The commercial terms named as unsettled on the terms page — the contracting entity, VAT treatment, refund position and governing law — are still unsettled, and are named there rather than implied. If your procurement needs a named contracting entity, VAT treatment or a data processing agreement, those are not published yet.