A credit plan is a fixed monthly price that buys credit for every service in your organization. An organization has at most one plan. You choose and manage it in the console under Billing > Plans, or with the plan API.
| Plan | Price a month | Credit a month |
|---|---|---|
| $8 plan | $8 | $11 |
| $20 plan | $20 | $25 |
| $100 plan | $100 | $150 |
Billing dates
- Plans run in calendar months in UTC. Each month’s price is charged to your default card on the 1st, and the month’s credit is added then.
- Your first month’s price and credit are prorated by the days left in the month, including today. If the prorated first charge would be under $0.50, the plan starts on the 1st of next month instead.
- In your first month, the plan’s credit pays for usage from the hour you subscribe. Usage earlier that month is billed as usual.
- You need a default card to subscribe. If the charge is declined, you don’t get the plan.
- Unused credit expires at the end of its month. It doesn’t carry over.
- Each plan charge is an invoice of its own. Your monthly invoice shows the plan credit it used like any other credit.
Changing or cancelling
- Upgrade applies at once: you’re charged the difference in price for the rest of the month, prorated, and get the extra credit, prorated the same way.
- Downgrade and cancel apply on the 1st of next month. Until then you keep the plan and its credit, and you can undo the change.
- After a plan ends, usage is charged to your card at list prices.
Over the API, subscribe with a tier (p8, p20 or p100)
and a mode (cap or overage), and change or cancel the plan by
sending its tier, mode and cancelAtPeriodEnd.
Hard cap and overage
Each plan has a mode. New plans start with Hard cap.
- Allow overage: usage past the month’s credit is charged to your card at list prices, on your monthly invoice.
- Hard cap: you never pay more than the plan price.
- When usage reaches 100% of the month’s credit, creating, starting, scaling up or resizing up
instances, autoscaling groups, Kubernetes clusters and node groups, databases and caches is
refused with the error
spend_limit_reached. - At 110%, running instances are stopped (except instance-store instances), and autoscaling groups, including Kubernetes node groups, are suspended with their instances stopped. Their sizes don’t change. Databases, caches and every other service keep running.
- Nothing is deleted. Stopped resources start again when your plan renews on the 1st of the month, when you upgrade, or when you switch to Allow overage. If the plan ends instead, they stay stopped until you start them.
- Usage past the credit appears on the monthly invoice with a Plan cap line that takes it off the total, so you don’t pay for it.
- When usage reaches 100% of the month’s credit, creating, starting, scaling up or resizing up
instances, autoscaling groups, Kubernetes clusters and node groups, databases and caches is
refused with the error
Switching from Hard cap to Allow overage charges usage past the month’s credit to your card, including usage earlier in the month. Switching to Hard cap during a month counts usage from that hour; usage earlier in the month is billed as usual, with your plan credit paying it first.
What the cap covers
The cap covers usage only. One-off purchases, such as domain registrations and renewals, are charged as usual and aren’t limited by it. Other credits you have, such as the alpha program’s, count toward the cap together with the plan credit.
Notices
You get a notice by email and in the console’s inbox:
- When usage reaches 80% and 100% of the month’s credit, in both modes.
- When resources are stopped under Hard cap, listing them.
- When a renewal payment fails, and when a plan ends because it kept failing.
If a renewal payment fails
A failed renewal is retried daily for 3 days. Under Hard cap, new resources are refused until the renewal is paid. If it still fails, the plan ends and usage is charged to your card at list prices. Under Hard cap, new resources stay refused until you subscribe to a plan again or switch to Allow overage.
Permissions
| Action | Allows | In |
|---|---|---|
billing.plans.get |
Viewing the organization’s plan | ReadOnlyAccess, BillingFullAccess |
billing.plans.update |
Subscribing to, changing and cancelling a plan | BillingFullAccess |