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 full audit trail, every user, every purchase and every entitlement — readable.
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. Engaging your users. Security and release notifications.
What Team adds
Members and roles. Scheduled checks against your Workers. Notifications fanned out. A shared record of who did what, and when.
What Enterprise adds
The compliance surfaces. 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.