Skip to content

Security and trust

A useful verdict starts with a narrow boundary.

DROP OS is designed to learn whether access works without collecting the secrets or customer records that make access possible.

Credentials stay with you

Provider credentials stay in your protected GitHub environment. DROP OS does not ask you to paste Stripe keys, database passwords or browser credentials into its dashboard.

  • GitHub OIDC for repository identity
  • No long-lived GitHub token required
  • Only narrow, redacted observation facts are submitted

Tenant boundaries are structural

Customer pages read through PostgreSQL's authenticated role and row-level policies, scoped to the verified account. Server-authorised writes and background maintenance use a separate privileged path with explicit ownership checks; they do not rely on row-level security alone.

  • Cross-tenant reads and writes tested separately
  • Deleting a workspace deletes only its own data
  • Repository and contract identities cannot be silently replaced

Evidence is checked before it counts

Every submission is checked for project, repository, workflow, commit and observer identity before it can affect your record. Duplicate deliveries and retries are safe.

  • Safe to retry
  • Handles results arriving out of order
  • Receipts that cannot be altered afterwards

This is the live service

This deployment is the live service: a dedicated application on its own domain, with an isolated schema and row-level tenant isolation inside our production Supabase project in London. Platform access is billed through DROP OS's own Stripe account, which is separate from the payment systems your project verifies — those are only ever described to us by facts your own workflow submits.

  • Isolated schema, tenant-scoped reads
  • Platform billing separate from the systems checked
  • Subscriptions are open; a trial still needs no card

What DROP OS can and cannot prove

DROP OS proves that the accepted observations agree and records where they came from. It cannot make a compromised customer-controlled runner honest, and it does not replace security, penetration, load or compliance testing.

  • No claim of SOC 2 or ISO certification
  • No claim that one run proves all future access
  • Uncertainty is reported instead of hidden

Review the boundary before connecting.

Questions about data handling or the verification model, and security reports, go to support@dropos.co. Please do not include credentials or customer records in the report.