Usage and billing on Voroa: build minutes and bandwidth
See your Voroa usage for this period - build minutes and bandwidth against your plan's included amounts - and how what is measured turns into your bill.
The Billing section of your Voroa dashboard shows how much you have used this period, so you always know where you stand. It is a read-only view — there is no payment step here.
What you see
Open Billing from the left navigation. For the current period you will see:
- Build minutes — the time spent building and deploying your services, shown against the build-minute pool included with your plan.
- Bandwidth (egress) — the outbound traffic your services served, in gigabytes, shown against the bandwidth included with your plan.
Each metric shows your usage, your included pool, and how much of that pool you have used. If your current plan has no included pool for a metric, you will see your raw usage without a limit. If a metric reads Not measured, we are not yet recording it for your workspace — that is not the same as zero usage, and we would rather say so than show you a number we did not take.
How usage is measured
- Build minutes are counted from the real build-and-deploy time of your services during the period. They are counted per account, across all of your workspaces.
- A build that fails still uses build minutes. The machine did the work — it fetched your dependencies and ran your build — right up to the point the build stopped, and that time is counted. We would rather tell you this plainly than have you find it in a number that does not add up. Preview-environment builds are the exception and are not counted against your pool.
- Bandwidth is the data every service in the workspace sends to the public internet — web responses, a worker’s outside API calls, an outside client reading your database — counted per workspace, with a table of how much each service sent. Traffic that stays inside Voroa, such as your app talking to its own database, is not counted against you. Bandwidth measurement is currently rolling out, so it may read “Not measured” on your workspace. How extra bandwidth is billed: Outbound bandwidth.
Usage is reported per billing period and resets at the start of each new period.
Billing status
Usage is measure-only today — Voroa tracks your usage so it is transparent, but nothing on this page charges you. No account has ever been billed for build minutes or bandwidth.
When that changes, it will not change quietly. Overage for build minutes used beyond your plan’s included pool would appear as its own named line on your GST invoice, showing the number of minutes and the month they were used in — never folded into a service charge or labelled simply “usage”. Two further things are worth knowing in advance, because they are properties of how it is built rather than promises:
- Usage is measured in calendar months, while your billing period runs from your own anchor day. So a month’s usage is billed on the cycle after that month closes, not the same one.
- Every plan carries a maximum on billable minutes, so the largest possible overage on a plan is a number you can work out in advance rather than an open-ended figure.
We will not enable this without the usage being visible to you first.
Choosing a plan on the pricing page
When you pick a plan or a size on the pricing page or a product page, Voroa remembers that choice while you sign in or create your account. After you sign in you land on the confirm screen for that plan, or on the create screen with that size already selected. You still review the price and confirm it there before anything is charged. If the plan you picked is no longer offered, you see the list of current plans instead.