- Documentation
- Billing
- Overage billing
Overage billing
Overage lets your services keep running even after reaching your plan limits. When enabled, extra usage is charged per unit consumed, as additional line items on your invoice.
What overage is
Each Guara Cloud plan has limits for CPU, RAM, storage, and build minutes. If you need more resources than your plan offers without upgrading, overage lets you go beyond those limits.
Overage is opt-in and never enabled automatically (except on Enterprise). You decide when to turn it on.
Availability by plan
| Plan | Overage |
|---|---|
| Trial | Not available |
| Starter | Opt-in |
| Pro | Opt-in |
| Max | Opt-in |
| Business | Opt-in |
| Enterprise | Included by default |
How to enable
Overage is enabled on your subscription, so the setting applies to every project in the account:
- Go to Settings in the dashboard.
- Open the Account tab.
- Under Overage Usage, click Enable Overage and confirm.
On the Enterprise plan, overage is already enabled and can’t be turned off. During the free trial the option is unavailable; it unlocks as soon as you choose a paid plan.
When you disable overage, resources above your plan limits are adjusted automatically at the end of the cycle.
Spend cap
With overage on, you can set a spend cap: the most, in BRL, that overage may cost per billing cycle. The cap is optional and can be changed or removed at any time in Settings > Account > Overage Usage.
- Tracking: the same screen shows how much overage the cycle has accrued against the cap.
- Warnings: you get an email and a dashboard notice at 80% of the cap and another when it is reached, once per cycle.
- At the cap: overage billing for the cycle stops at the cap — you never pay more than it. Builds past your plan’s included minutes pause until the next cycle or until you raise the cap. Your services keep running.
- New cycle: the accrued amount starts from zero at the beginning of each billing cycle.
If you lower the cap below what the cycle has already accrued, it applies right away: nothing more is billed for the cycle and builds past the included minutes pause. Overage already recorded before the change stays on the invoice.
Overage rates
Overage is charged at the end of the billing cycle, based on measured usage. The same rates appear in the dashboard under Overage Usage:
| Resource | Price |
|---|---|
| vCPU beyond the pool | R$ 4/vCPU-hour |
| RAM beyond the pool | R$ 2/GiB-hour |
| Build minutes beyond the quota | R$ 0.03/minute |
| Storage beyond the project total | R$ 2.50/GiB-month |
How the calculation works
- CPU and RAM are measured in hours: vCPU-hours and GiB-hours. Your plan includes the account pool for the whole cycle (the pool times 730 hours). Only the hours above that are charged, so you pay only for the time you actually used extra resources.
- Build minutes beyond the monthly quota are charged per minute.
- Storage beyond what your plan includes is charged per GiB-month.
Example: if you use 0.5 vCPU beyond your plan’s pool for 12 days, that’s 144 extra vCPU-hours (0.5 × 12 days × 24 hours). At R$ 4/vCPU-hour, the CPU overage comes to R$ 576.
Safety limits
Overage still respects your account resource pool, namespace quotas, and the platform’s safety limits for your plan. It gives you headroom beyond the allowance included in self-serve paid plans, but it doesn’t bypass Kubernetes admission or the platform’s reliability guardrails.
When a safety limit is reached, the behavior is the same as reaching your plan limit without overage — your services keep running, but new resources can’t be allocated. To go beyond those limits, you need to upgrade your plan.
Bandwidth and overage
Bandwidth is unlimited on all plans (fair use) and isn’t part of overage. You’re never charged for network traffic.