Billing
Billing, plans, and usage
How customers understand plans, credits, usage, invoices, top-ups, and suspended account states.
Created from Phase 2 docs inventory and customer billing journey planning.
What billing controls
Billing controls the commercial side of Kaidera: plan access, project and worker allowances, usage, invoices, credits, top-ups, and what happens when an account reaches a limit.
Plans
Plans define the level of access a customer receives. Plan details can include available product surfaces, worker allocation, support level, project limits, enterprise controls, and custom model or deployment options.
Credits and usage
Usage should be visible to customer admins in plain language. Admins should understand how credits are consumed, which projects or workers are active, and whether any model/provider usage needs attention.
Top-up and auto top-up
Where available, top-up lets an admin add credits. Auto top-up can reduce interruption risk, but it should be configured with clear approval and spending expectations.
Invoices and payment methods
Admins should be able to review invoices, payment methods, transaction history, and account status without needing to ask support for routine billing visibility.
Hard stop and suspended state
If a plan or credit balance reaches a hard limit, Kaidera should make the account state clear. Users should see what is paused, what remains viewable, and what the admin needs to do next.
What can go wrong
Billing confusion usually comes from unclear plan limits, missing usage visibility, no named billing owner, or users not knowing which actions are paused when limits are reached.
Read next
Read Customer admin and settings for role and access configuration. Read Support if billing needs escalation.
Website context
Connect this guide back to the product story
The technology docs map links this page to the public technology narrative and helps buyers move from a capability overview into the right operating guide.
Open technology docs map →