Kvindo™ Cloud Docs
A Billing Account holds the monetary balance for an organization. Every provisioned resource meters usage and draws down this balance. The account is created together with the organization; it has no configurable spec — you read its balance and top it up.
• Balance — the current funds available, in rubles (status.rubBalance); resource usage draws it down continuously
• No spec — the account carries only metadata (its name) and status; there is nothing to configure at create time
• One per organization — created automatically with the organization; keep the balance positive to avoid resource suspension
| UI Name | API / kc name | Terraform name | Optional | Format | Default | Is read only | Description |
|---|---|---|---|---|---|---|---|
| Balance | status.rubBalance |
status.rub_balance |
— | decimal — RUB | — | Yes | Current account balance in rubles |
status.pricing fields (shown under "All fields") are meaningless for a Billing Account — they would report the resource's own cost, which is zero; the account balance above is what matters. And the console's billing page offers much more than the API exposes here — top-ups, on-demand invoices, downloadable monthly closing documents (acts), transaction history, and per-resource charge breakdowns.The account has no spec, so the useful operation is reading the balance.
Python SDK
kc CLI
Resource docs
Reference