Check compatibility first
- A GitHub repository where you can commit workflow files, add Actions secrets and run workflows. Have its owner, name, numeric repository ID and deployment branch ready. The GitHub repository API returns the numeric
id; it is different fromnode_id. - A Stripe test customer with a subscription and the price you expect that subscription to use. Prepare a restricted test-mode key with read access to subscriptions.
- A Supabase project with a dedicated email/password test account whose email is confirmed, and its publishable key — the one that starts
sb_publishable_(Project Settings, API Keys). The legacyanonkey is not accepted. You need permission to adapt a database function that reads that account’s access. - If Vercel Deployment Protection covers the staging deployment, the check cannot sign in or read its release endpoint. Serve the staging branch from an address that protection does not cover before you start.
- An HTTPS login page and a protected page on the same origin. The browser check uses email/password fields and a submit button, expects login to redirect to another path, and looks for your chosen success selector on the protected page. SSO, MFA and other login flows are not supported by this adapter.
- For proof tied to an exact release, an endpoint on your app that returns its deployed Git commit. Without that endpoint, the result covers the application that answered, rather than proving which release served it.
Create a workspace and verify the repository
Create your account, confirm your email, then enter your organisation, application and repository details in the workspace setup. The three-day trial starts when your first workspace is created.
- Choose the branch that deploys your staging app and the workflow filename, for example
staginganddropos.yml. A check starts after each successful Preview deployment of that branch’s latest commit. On Vercel your production branch, usuallymain, deploys as Production, so a staging check needs a different branch. - Use the repository’s permanent numeric ID, not its name: run
gh api repos/OWNER/REPO --jq .id, or view your repository page’s source and search forrepository_id. - Save the one-time verifier shown after setup as the Actions secret
DROP_OS_BINDING_VERIFIERin that repository. It is shown only once. - Copy the repository-verification workflow from your project page into
.github/workflows/dropos.yml, using your chosen filename. Commit it to the registered branch and to your default branch — GitHub only offers Run workflow for a file that exists on the default branch — then run it manually from GitHub Actions on the registered branch. - Return to the project page and confirm the repository is verified. A verified repository alone does not mean an access check has run.
Prepare the customer and app access check
Use the same dedicated customer across Stripe, Supabase and your app. Map its Stripe customer ID, expected price, and the access your app grants to that account.
In Supabase, adapt dropos_read_entitlement to return exactly one column, plan_active, as a boolean for the signed-in test account — any other column is refused. It must respect your row-level security rules. The following example assumes public.profiles has an id matching the account and a plan equal to pro; change those assumptions to match your app before using it.
create or replace function public.dropos_read_entitlement()
returns table(plan_active boolean)
language sql stable security invoker
set search_path = ''
as $$
select coalesce((
select p.plan = 'pro'
from public.profiles p
where p.id = (select auth.uid())
), false);
$$;
revoke all on function public.dropos_read_entitlement()
from public, anon;
grant execute on function public.dropos_read_entitlement()
to authenticated;Check the grant actually took effect. On Supabase, revoke … from public does not always restrict a function on its own: default privileges can re-grant EXECUTE on newly created functions, so the revoke silently does nothing. Run select has_function_privilege('anon', 'public.dropos_read_entitlement()', 'execute'); and confirm it returns false before you continue. This function is security invoker and resolves auth.uid(), so an anonymous caller would receive false rather than anyone's data — but it should not be callable at all.
Add these Actions secrets to your repository: DROP_OS_STRIPE_RESTRICTED_KEY, DROP_OS_SUPABASE_PUBLISHABLE_KEY, DROP_OS_TEST_EMAIL and DROP_OS_TEST_PASSWORD. Use the restricted Stripe key and dedicated account described above. Do not paste credentials into DROP OS or send them to support.
Configure and install both workflows
After repository verification, your project page provides an access-check workflow and a deployment-trigger workflow. Replace the temporary verification file with the access-check file, keeping its registered filename. Add the companion file too: for dropos.yml, it is dropos-deployment.yml. Both belong in .github/workflows/.
- Fill in the form on your project page — Stripe customer and price IDs, Supabase project reference, app address, login and protected paths, success selector and any extra hosts. The file updates as you type; nothing you enter there is saved or sent to DROP OS. The rest of this list says what each value means if you edit the file by hand.
- The Stripe customer and expected price are your test customer’s IDs, from the same Stripe mode as the key.
- Fill in your Supabase project reference, canonical
https://<project-ref>.supabase.coURL, schema and access-check function name. Custom Supabase domains are not accepted by this adapter. - Set the login URL, protected-page URL, allowed network hostnames and success selector. The success selector must identify content visible only after the expected access is granted. Include your app host, the canonical Supabase host, and every asset or API host the journey requests in the allowlist. Unlisted requests are refused.
- The login selectors default to
input[type=email],input[type=password]andbutton[type=submit]. If your form differs, setemail-selector,password-selectorandsubmit-selectorin the workflow. - Set the release endpoint and commit-field name if you need the exact-release check.
- Keep the generated project, repository, branch and action-version values. The generated trigger expects a successful GitHub deployment labelled
Previewfor staging, orProductionfor a paid production target. Commit both files to the registered branch and to the repository’s default branch: GitHub starts a dispatched workflow only when its file also exists on the default branch. After each successful deployment of the registered branch’s latest commit, the deployment trigger starts the access check on that branch.
Review the completed files before running them. The template is not ready to run while example URLs or REPLACE / YOUR_ placeholders remain.
Run a check and read the result
Run the access-check workflow manually on the registered branch to diagnose setup. Then make a successful staging deployment to test the automatic trigger. Open the resulting check from your DROP OS project.
- Pass: the accepted subscription, app access and browser observations agree for this check.
- Mismatch: the observations disagree. The trial identifies the disagreement; the paid plan also provides evidence, investigation steps and owner email alerts.
- Could not verify: the check could not gather enough evidence. This is not a pass and does not use a completed-check unit.
Your team makes any repair. A later check confirms whether access has recovered. One result does not prove every customer or feature works.
If you do not get a result
- Repository still pending: check the numeric repository ID, registered branch, exact workflow filename and one-time verifier. Use the project’s verifier controls if it has expired.
- No automatic workflow run: open the run of the deployment-trigger workflow in GitHub Actions — it says whether it started a check and, if not, why. The usual cause is a deployment that was not of the registered branch’s latest commit. If there is no trigger run at all, confirm both files are on the default branch and the registered branch, and that the deployment reports success to GitHub with the environment label shown in the generated file. Use a manual run to separate trigger problems from check problems.
- Configuration or login failure: remove remaining placeholders; check the restricted key’s mode, Supabase function, test credentials, network allowlist and success selector in the GitHub Actions log.
- Checks paused: read the allowance message in DROP OS. Trial expiry, completed-check limits and total-attempt limits are separate. See pricing and limits before retrying.
Still blocked? Contact support with the check reference and error wording. Exclude credentials and customer records.