Billing issues
Fix payment, invoice, and subscription problems.
Use this page when your plan, seats, cloud usage, or payment method looks wrong, or a cloud workspace won't start for billing reasons.
Check:
- You're looking at the right billing scope. Personal billing and organization billing are separate. If you're a member of an org, confirm whether the thing you're checking (a plan, a credit balance, a payment method) belongs to you or to the organization.
- Your plan matches what you expect. Free, Core, or Enterprise, each with its own included usage.
- Seat count is right, for organizations. Org plans bill per seat; adding or removing members changes what you're charged next period.
- You're checking the right kind of credit. Proliferate meters two separate things: compute units, spent by cloud sandboxes and hosted runtime, and LLM credits, spent by model calls through the managed gateway. They don't draw from the same pool, and running out of one doesn't affect the other.
- Overage is set up the way you want it, for compute. Compute usage can extend into paid overage if you've enabled top-up and haven't hit your cap. LLM credits work differently: they're hard-capped, so once they're used up, gateway-routed model calls stop until the next billing period or until you add more, whichever your plan supports.
- Payment is actually going through. A failed card blocks new cloud usage even if you technically have credits left.
Settings > Billing
The Billing settings pane: current plan card with a Manage plan action, a compute units balance (purchased/available/used, with an Add compute units action), an LLM credits balance, an auto top-up toggle for overage, and a Billing portal button.
When a cloud workspace can't start or wake up for billing reasons, the banner names the specific cause instead of a generic error:
| What you'll see | What it means |
|---|---|
| Included usage is exhausted | Your included compute for this period is used up. |
| Overage is disabled | You're out of included usage and haven't turned on top-up. |
| Overage cap reached | Top-up is on, but you've hit the cap you set. |
| Payment needs attention | A charge failed; update your payment method. |
| Sandbox limit reached | You already have the maximum number of sandboxes running at once. |
Raising your overage cap or enabling top-up only affects compute units. If you're seeing gateway/model errors instead of a workspace-start block, that's the separate, hard-capped LLM credit pool, not overage.
Invoices, receipts, and payment methods live in the billing portal, reached from the Manage plan action in Settings. See plans and usage and limits for the full model.
If the symptom is specifically a cloud workspace that won't start, see cloud workspace issues too.