Billing for your organization
How an organization is billed: seats bought and managed in the dashboard and paid through a payment portal, or an Enterprise agreement invoiced by purchase order. Who can see it, and where invoices live.
An organization is billed as an organization. Individuals in it do not pay for their own use, and the money side is kept to the roles that should see it.
Two ways an organization pays
By seat, through a payment portal. Seats are bought and managed from the dashboard, and the card, the invoices, and the billing details live in a payment portal you open from there. Adding a seat or moving one between people does not need anyone to contact us.
By invoice, on an Enterprise agreement. Billing is by invoice or purchase order rather than by card, against the terms agreed with us. Your finance team gets documents it can process, and the seats are part of the agreement rather than a shopping action.
If you are not sure which one applies to your organization, the Billing section of the dashboard shows what your organization is on.
Who can see it
The billing role and the owner. That role is about invoices and seats and nothing else: it cannot touch the model or connector allowlists, which are a different kind of decision. See Roles and permissions.
Where the numbers are
Billing holds invoices, seats, and the subscription. Usage holds what was actually used: requests, cost, tokens, and cache savings, broken down by member, model, and surface.
Usage is counts and cost only, never the contents of anyone's work. See What is recorded about every request.
If a payment fails
When payment is the reason, the organization is suspended, and requests pause for everyone until it is settled. Nothing is deleted, and access returns as soon as payment clears. The blocked screen names which of the two it was, an overdue invoice or a failed method, because the way out is different. A suspension can also be set for something else, and the reason it names is the one that applies.
See Organization status: what each one means.
Related articles
- Organization status: what each one meansActive, on hold, suspended, cancelled, and terminated. What each state does, why only two of them can be reviewed, and what happens to your work in each.
- Your organization dashboardWhat each section of your organization dashboard holds, from members and teams to usage, billing, policies, the audit log, and the conversation archive. And who can see which part.
- Roles and permissionsThe six roles in a Dropstone organization, what each one may do, why reading member conversations is deliberately not an administrator power, how administrators are appointed, and what the gold verified mark means.
- Compare plansDropstone has a Free plan, Pro, Max, and Enterprise. Every plan includes memory across chat, CLI, and SDK. Plans differ in weekly usage, which models you can use, and team features.
- Manage your subscriptionUpgrade, downgrade, switch between monthly and annual, update your payment method, or cancel, all from the billing page in your Dropstone dashboard. What changes when, and what happens to your data.
- What is recorded about every requestEvery request records the model, the tokens, the cache hits, the cost and the timing, on every account and whatever your training settings are. What that record holds, who can see it, and what it never holds.