The commercial terms are still being settled. The billing entity, VAT treatment, refund terms and governing law are not published below, because they are not settled. Subscriptions are open; none of those should be inferred from the fact that a price is shown.
The service
DROP OS accepts release-bound observations from a GitHub workflow you install in your own repository, and derives a verdict on our server about a paid-customer access promise you define. It keeps the run history, the evidence behind each verdict and repair guidance naming the boundary that failed.
What you pay
£29 per month for one application, including 500 completed checks each calendar month. A completed check is one that reached a verdict; a run that fails technically or is abandoned does not spend one, and a retry of the same deployment is the same check. Before that, a trial of 3 days and 10 completed checks on a staging application, with no card.
Cancelling
Monthly, from the Stripe billing portal, at any time. Cancelling takes effect at the end of the period you have already paid for, and access continues until then. We do not charge you without a subscription you started yourself.
What a verdict means
A verdict reports whether the accepted billing, entitlement and browser observations agree for one bound release and one access promise. It does not prove every feature works, guarantee future access, identify every root cause, or replace security, penetration, accessibility, load or compliance testing.
Runner trust boundary
The workflow runs in your environment, not ours. DROP OS verifies the declared origin and the internal consistency of what it receives, but it cannot make a compromised runner or compromised credentials truthful.
What runs without you
Your deployment starts a check. After that the hosted worker settles checks that are still waiting, retries a notification that could not be delivered within bounded limits, and purges evidence at 30 days. None of that needs you to re-run anything.
What the service does not do
We do not start checks on a timer: a check begins when you deploy, not every hour. We do not call a webhook of yours when something happens — results reach you by email and in the dashboard. The product does use Stripe’s webhooks to hear about your own subscription, which is a different thing. Evidence is kept for 30 days and there is no longer-retention option.
Your responsibilities
You must be authorised to connect the repository and the services you point it at, keep provider credentials in your own GitHub environment rather than sending them to us, and review the generated workflow before running it.
Availability
No availability or response-time commitment is made. This is a single-operator service in its first weeks of running — the same limitation described elsewhere on this site, stated once here in the terms that bind it; keep your own source, configuration and operational records.
Deletion
You can delete eligible projects, workspaces and your account from the settings screens. Account deletion asks for explicit confirmation and recent authentication. Where an external provider is temporarily unavailable, the cleanup is safe to retry.
Not published here, because it is not decided
The contracting entity and company number, the address for notices, the VAT treatment of the £29 price, the refund position, and the governing law and jurisdiction. None of these is stated anywhere on this site, and none should be inferred from the fact that a price is shown.
Contact
support@dropos.co, which is the support and disclosure address for the service. It is not an address for legal notices: that is one of the items above that is not settled. Never send credentials, card details or customer data through it.