Base rates
Hourly figures use a 720-hour billing month ($1 ÷ 720). Billing tracks usage over the cycle; apps that are scaled down or stopped cost less than always-on capacity.
How usage is measured
- You choose CPU and memory when you create or resize a project (or database).
- Brimble tracks how long that capacity runs during the billing cycle.
- The charge is proportional: half a month at 2 vCPU costs about half of a full month at 2 vCPU.
Region multipliers
Most regions bill at the base rates above. Some regions cost more because infrastructure is more expensive there. When that applies, the dashboard shows the effective CPU and memory rate for the region you pick (base rate × regional factor). For example, if a region uses a 1.45× factor:
Always check the rate shown at create or resize time for the region you selected. Details: Regions.
Estimate your cost
Use the pricing calculator to model plan, seats, CPU, memory, and region before you deploy. Base rates and region multipliers on this page still apply; the calculator turns them into a full monthly estimate.What is not included here
Compute pricing on this page is CPU and memory only. Separately:- Bandwidth overage, volume storage, object storage, sandboxes, backups, and add-ons — see How billing works.
- Build minutes — see Build minutes.
Tips to control spend
- Right-size CPU and memory; don’t leave unused headroom running.
- Prefer a region close to users that also matches your budget (check the rate in the UI).
- Use a spending limit if you want a notify or pause threshold.
- Watch the live billing estimate during the cycle.