Billing and limits
Root & Branch Cloud bills based on the resources your workloads consume. Each workspace has an independent billing configuration.
How billing works
Section titled “How billing works”Every component in your workspace - apps, databases, and buckets - is tracked for usage duration. Usage records are generated per-component and linked to pricing SKUs.
Resource tiers map to billable SKUs:
| Tier | CPU | Memory | App SKU | Database SKU |
|---|---|---|---|---|
| Micro | 0.5 | 512 Mi | app.micro |
db.micro |
| Small | 1 | 1 Gi | app.small |
db.small |
| Medium | 2 | 2 Gi | app.medium |
db.medium |
| Large | 4 | 4 Gi | app.large |
db.large |
| X-Large | 8 | 8 Gi | app.xlarge |
db.xlarge |
In addition to compute, storage is billed per GiB under the storage.app.gib and storage.db.gib SKUs. Billing starts when a component reports as running and ends when it is deleted or stopped.
Setting up billing
Section titled “Setting up billing”Billing is configured per workspace via GoCardless direct debit. To set it up:
- Go to Workspace Settings > Billing.
- Click Set up billing.
- You are redirected to GoCardless to authorise a direct debit mandate.
- After authorisation, the platform links your GoCardless mandate to the workspace.
Only workspace owners can set up or disconnect billing. Disconnecting removes the payment method and stops new usage from being invoiced against that workspace, but does not cancel existing invoices.
Invoices
Section titled “Invoices”Invoices are generated automatically by background workers. Each invoice contains line items broken down by:
- Component name and type.
- Resource tier SKU.
- Storage used.
- Usage period.
Invoices progress through several states: draft → finalised → payment_pending → paid. Failed payments are retried and may be carried forward to the next billing period.
Viewing invoices
Section titled “Viewing invoices”Invoices are listed on the billing page, paginated with the most recent first. Each invoice shows the total amount and individual line items.
Paying invoices
Section titled “Paying invoices”Successful invoices are collected automatically via GoCardless. If a payment fails (e.g. insufficient funds), you can trigger a manual payment from the dashboard.
The platform enforces a minimum collection amount of 1.00 in your workspace currency. Amounts below this threshold are carried forward.
Credits
Section titled “Credits”Workspaces can have a credit balance. Credits are applied to invoices automatically before a payment is collected. You can view your current credit balance from the billing page.
Estimating costs
Section titled “Estimating costs”The billing page shows an estimated usage cost based on your current running components. This is a projection of what the next invoice might look like and helps you track spending between billing cycles.
Restrictions
Section titled “Restrictions”If invoices remain unpaid beyond the allowed window:
- The workspace becomes restricted.
- Running apps and databases are scaled down to minimal resources.
- Resources that remain unpaid for an extended period may be deleted permanently.
Paying the outstanding balance removes the restriction. Apps and databases return to their configured resource tiers automatically. You can monitor restriction status from the workspace settings.