Billing
A prepaid rial wallet per team. Usage is rated hourly, and an invoice is issued for each Jalali month with charges.
Plans#
| Plan | How it is charged |
|---|---|
| Hobby | Free, up to the plan's included amounts. When they run out the sites pause until next month; nothing extra is charged. One developer, the owner; viewers and billing members free. For non-commercial use. |
| Pro | A monthly fee per developer seat (owner, admin or developer) from the wallet; each seat's fee comes back as the same amount of usage credit. Usage past the credit is charged from the wallet, up to the monthly spend budget. |
| Enterprise | Custom. |
The amounts and included usage of each plan are on pricing, read from the same price list the invoice is made from.
cloudhost billing
# plan hobby
# balance 0 tomans
# period 1405-08: usage 0 tomans
cloudhost billing plan proMoving to Pro takes the whole month's fee for every developer seat in the team, plus VAT, from the wallet at once, so the wallet must hold it. Moving back to Hobby gives no refund, and the team must have one developer only.
Developer seats#
| What happens | On Pro |
|---|---|
| Who counts | Every member with the owner, admin or developer role. Viewers and billing members are free. API keys are not members. |
| The first of each Jalali month | The fee × the developer seats, plus VAT, comes out of the wallet, and as much usage credit comes in. |
| Adding someone mid-month | A new member with a developer role, or a viewer or billing member promoted to one: the days left in the month (the day itself counted) come out of the wallet at once, and as much credit is added. |
| Removing or demoting | No refund. The seat stays paid to the end of the month, and someone added in the same month takes it at no charge. It is not counted from the next month. |
| If the wallet cannot pay | The invite or promotion is refused, and the error says what the seat costs and how much to top up. |
On Hobby only the owner is a developer; add others as viewers or billing members, or move the team to Pro. The seat count and the next seat's cost are in GET /v1/billing (the seats and seat fields).
The wallet and top-ups#
cloudhost billing topup 500000
# pay 500,000 tomans by card payment:
# https://…
cloudhost billing transactionstopup takes the amount in tomans and returns a payment page link. Payment is by a Shetab bank card, and the wallet is credited when the bank confirms. The command itself charges nothing.
A top-up is 10,000 to 200,000,000 tomans. The card is not stored and nothing is charged automatically.
If a Pro wallet goes below zero, after a grace period the team's sites are suspended and show a payment-required page until the wallet is topped up.
Usage and prices#
cloudhost billing usage --period 1405-08
cloudhost billing pricesEach meter's usage (requests, compute, storage, traffic, …) is rated hourly within the current Jalali month. Periods are Jalali months written YYYY-MM, for example 1405-08 for Aban 1405.
Invoices#
cloudhost billing invoices
cloudhost billing invoice 1405-000001
cloudhost billing invoice preview # this month so far, not issuedFor each Jalali month with charges, an invoice numbered <year>-<6 digits> is issued when the month ends, with the usage lines, the usage credit used (or the free amounts) as a discount, the seat fees (developer seats × the month's price, and one line for each seat added mid-month with its days), VAT, and the wallet's statement for the month.
Set the buyer's details (person or company, national code or national id, economic code, postal code and address) in the dashboard; they are copied into each invoice when it is issued.
The monthly spend budget#
Pro has a monthly spend budget you can change. With "pause at the budget" on, the team's sites pause when the month's spending reaches it, and nothing more is charged.
curl -X PUT https://api.ibel.ai/v1/billing/spend \
-H "Authorization: Bearer $KEY" \
-d '{"limit":80000000,"pause":true}' # rialsIn the API every amount is in rials (1 toman = 10 rials). Changing the plan, the budget and the tax details needs the owner, admin or billing role, and from the dashboard a second factor.