How Brimble billing works

Brimble billing has four parts:

1. A recurring plan charge (or the Team charge).
2. Metered usage for compute and other resources you run during the cycle.
3. One-off purchases, such as build-minute top-ups.
4. Invoices, payment recovery, and spending limits.

This page explains how those pieces fit together. For a full breakdown of CPU and memory rates, see Compute pricing.

​

Two billing scopes

• Personal billing covers your personal workspace.
• Team billing covers a specific team workspace.

These are independent. Upgrading your personal plan does not change a team subscription, and changes to a team subscription do not affect your personal workspace.

​

Plans

Paid plans need a payment method and an active subscription. Free does not.

​

What the plan price covers

The plan (or Team charge) covers platform access and the allowances listed on brimble.io/pricing and in the dashboard, for example included bandwidth, build minutes, and sandbox allowances where your plan has them. CPU and memory are not included in the plan price. Anything you provision is metered. See Compute pricing.

​

Starting a paid subscription

You need:

• A payment method on file.
• Acceptance of the billing terms.

When the first payment succeeds, the subscription becomes active immediately. If your card needs extra confirmation, finish that step before activation completes.

​

Team billing

Team workspaces have their own subscription. The Team charge is based on how many people are in the workspace:

• $11/month covers up to 3 members, including you.
• Each member after the third adds $11/month.
• Only members who have accepted their invite count. Pending invites cost nothing.

The charge follows your team automatically. When someone accepts an invite, leaves, or is removed, the Team charge updates and the change is prorated for the rest of the cycle. There’s no seat count to manage. Team workspaces use the same plan allowances as Developer, including bandwidth, build minutes, concurrent builds, sandboxes, and feature flags. The difference is shared membership and workspace billing, not a richer entitlement tier.

​

Team billing ownership

A Team subscription has a billing owner: the person whose payment method is charged for that team. Billing ownership can be transferred when:

• The team subscription is active and not pending cancellation.
• There are no open invoices for that team.
• The new owner is an accepted Creator or Administrator on the team.
• The new owner has a payment method on file.

The remaining billing period is preserved during the transfer.

​

Billing cycles

Paid subscriptions renew on a monthly cycle. Brimble uses that window for:

• Your next renewal date.
• Build-minute resets on paid plans.
• Usage estimates for the current cycle.
• Trial end handling.

​

Upgrades, downgrades, and cancellation

​

Upgrades

Moving to a higher personal plan applies immediately when payment succeeds. If your card needs confirmation, finish that step before the change completes.

​

Downgrades

Moving to a lower personal plan is scheduled for the end of the current billing period. Your current plan stays active until then. You can cancel a pending change before it takes effect.

​

Cancellation

Canceling a paid subscription schedules it to end at the end of the current billing period. When the period ends, the workspace leaves the paid plan.

​

Trials

Brimble offers a one-time Developer trial for eligible personal accounts:

• Available to Free and Hacker users.
• Once per account.
• Requires a payment method before it starts.
• The trial lasts 7 days.

You get a warning before the trial ends. If it ends without a usable payment method, the trial cancels instead of converting unpaid.

​

What else appears on your bill

Besides the plan or Team charge, a cycle can include: The dashboard estimate updates through the cycle so you can see where spend is coming from before the invoice closes.

​

How your bill is calculated

1. Start with the plan charge (or the Team charge for your accepted members).
2. Add metered usage for that cycle (compute, bandwidth overage, storage, sandboxes, and so on).
3. Add any one-off purchases in the same cycle.
4. Apply any credit on your account balance.

​

Estimate before you deploy

For a full monthly estimate (plan or team size, CPU, memory, region), use the pricing calculator. Rates and how the bill is built are covered in Compute pricing. Quick orientation:

• Hacker starts at $3/month for the plan, plus metered compute and other usage.
• Developer starts at $11/month, plus metered usage.
• Team starts at $11**/month for up to 3 members, plus **$11 per extra member and metered usage for that workspace.
• Build-minute top-ups are separate one-off charges.

​

Usage estimates and invoices

• A live estimate for the current cycle (base plan, metered breakdown, open invoice totals).
• Invoices for settled and open charges.

​

Open invoices block some billing actions

Outstanding invoices can block:

• Starting a new paid subscription.
• Changing a personal plan.
• Updating the Team charge when members join or leave.
• Transferring Team billing ownership.

Settle open invoices first, then retry the change.

​

Paying an invoice manually

If you have a default payment method, Brimble tries that card first. If off-session payment cannot complete, you can finish on the hosted invoice page. When wallet credit is available and card payment cannot complete, Brimble can settle the invoice from your wallet instead. See Wallet. When payment succeeds and nothing else is outstanding, billing locks clear and features paused for non-payment can turn back on.

​

Payment failures and recovery

When a renewal fails, Brimble records the attempt, notifies you, and waits for the subscription status to update. Subscriptions that stay unpaid for 30 days or more are canceled.

​

Build minutes

Included minutes reset each paid renewal cycle (or monthly for free accounts). Purchased top-ups carry forward until used. See Build minutes.

​

Spending limits

Optional spending limits on personal accounts and team workspaces:

• A dollar amount (minimum $5).
• An action: notify or pause.

Notify warns you and keeps compute running. Pause warns you and disables builds and sandboxes until usage drops below the limit or you raise it.

​

Payment methods

You can save, list, remove, and set a default card. The default method is used first for renewals and invoice attempts. Some cards require an extra confirmation step (for example 3D Secure).

​

One-off purchases

Separate from the recurring plan:

• Build-minute top-ups
• Agent token top-ups
• Domain purchases and renewals

Minimum for build minutes and token top-ups is $5.

​

Domain auto-renewal

Domain renewals are billed separately from your workspace plan. When auto-renewal is on, Brimble creates a dedicated recurring charge anchored to the domain’s renewal date. Failed renewals notify you; duplicate charges can be refunded when appropriate.

​

Refunds

Successful one-off charges can be refunded through the original payment channel when the transaction is eligible. Pending or already-refunded transactions cannot be refunded again.

​

Weekly usage insights

Active paid subscriptions can receive a usage report for the current window (base plan, metered totals, and major contributors). Production accounts may also get a scheduled weekly summary email.

​

What to expect in the dashboard

• Add or confirm a payment method
• Start or change a subscription
• Review the live billing estimate
• Pay an open invoice
• Set or raise a spending limit
• Buy extra build minutes
• Enable or cancel domain auto-renewal
• Share a referral code and redeem referral credits

​

Next steps

• Pricing calculator, estimate plan, team size, and compute before you deploy.
• Compute pricing, CPU and memory rates, hourly equivalents, and regions.
• Build minutes, top-ups and monthly resets.
• Referrals, referral codes, domain coupons, and invoice discounts.
• Regions, how region choice affects latency and price.
• Persistent disk, storage that contributes to usage billing.