The rule that decides everything else
The dashboard is what you are paying for, what it never stores is what you are not, your subscription is your current one, and roles and permissions is what a seat buys.
The kit is free. All of it. Always.
Every capability stays fully usable from the CLI and your Worker’s API regardless of what anyone pays.
What has a price is the admin interface: the browser screen your team uses to run the application, and the work of keeping it working.
Four plans
| For | |
|---|---|
| Free | What an account is on before anything is granted. No time limit |
| Solo | One person, working from a browser rather than a terminal |
| Team | Several people, sharing the work and the record of it |
| Enterprise | An organization that has to show its work |
Current prices are on the pricing page, which quotes them live rather than restating them here.
Reading is free, forever
Free covers the newest audit events, every user, every organization and its roster, every purchase and every entitlement — readable. And the privacy inventory: which fields hold PII, PHI, PCI or secrets in each environment, read from the deployed code, with its findings and its export.
Plus the CLI and your Worker’s API in full.
The paid part is acting on production from a browser, and the surfaces that come with doing it as a team.
What Solo adds
Acting on your own data without a terminal. Secrets rotation. Comping and revoking an entitlement, and pinning one customer’s allowance. Answering a support thread: replying, closing or reopening it, classifying it again, and marking it read. Sending a failed email again, and blocking or unblocking an address on the suppression list. Managing your testers: inviting, resending an invitation, nudging and removing. Security and release notifications.
What Team adds
Members and roles. Engaging your users. Alerts: failed renewals, drifting webhooks, a reconcile that stopped and testers about to lapse, checked hourly against your Workers at thresholds you set. Notifications fanned out. Billing administration: running reconciliation, overriding a payment and setting a discount. Revenue integrity: who pays and is locked out, and who is entitled and does not pay, across every rail, ranked, each row ending in its fix; the count of each is on every plan. The environment notice: which environment runs which version of each module, and since when we first saw it. Access review: the scopes each credential holds and has not used, and the command that narrows them. Access attestation: who could reach your data, now and on any day the trail keeps, by kind of scope, and what each agent and script was allowed to call. Shared triage: assign a support thread, filter the inbox by who has it, and see who else has it open. Audit explorer: search the audit trail by actor, action, outcome and range, over whatever your Worker keeps, and tell an agent’s acts from a person’s. Data-subject export: everything every capability holds on one person, as one file, and what it could not reach. Account administration: suspend, reinstate, delete and restore your users and organizations, and administer an organization’s members, with a reason on every act. Revoking a repository’s tokens: take back one git token, or every live one, on a repository your app hands out. Moderating a leaderboard: hide, unhide or correct an entry, and clear a stale refresh lock. Closing a game session and voiding a result: close a stuck session, or void a result so it stops counting and the leaderboard and rating take it back. Recalculating and resetting a rating: rebuild a player’s rating from their logged outcomes, or return it to where its algorithm starts. Dropping a player and canceling an invite: drop a player from a game’s queue, telling them why, or cancel a pending invite. Correcting a ledger: credit or debit a player’s balance, reverse an entry or release a hold, each with a reason and moved once. Reports: several questions’ answers in one document, run live from your Worker, printed to PDF or exported as JSON, and stored nowhere. A shared record of who did what, and when.
What Enterprise adds
Evidence: the evidence an auditor asks for, derived by your Worker, in seven sections: the evidence pack, the audit trail’s chain, erasure, SIEM, retention and holds, consent, and the record of processing, each exported as JSON as your Worker answered it; and placing or releasing a legal hold. Privacy history: we watch the privacy inventory, record every change with its build, and mail you when a field loses its marker, with history kept thirteen months by default and up to six years, and a periodic posture report an admin turns on. Saved reports: a report’s definition and a log of who ran it when, so it runs again the same way, never its answers. Custody of credentials, and scoped API tokens. A contract.
What you are paying for
Not access to data you already own.
The UI, the workflows, and their upkeep. Everything the dashboard reads lives in your D1 and is reachable with a credential you minted, whatever you pay — the paid part is not having to write the screen yourself.
What happens if you stop paying
Your data is unaffected, because none of it was ever here.
Your Worker keeps running. The CLI keeps working. The connection is a row in your own database, and it is yours to keep or delete.