Outbound bandwidth: what counts and what it costs
What outbound bandwidth Voroa counts for every service in a workspace, how much each plan includes, how extra use is billed, and where to see usage by service.
What counts
Outbound bandwidth is the data your services send to the public internet: every page, image and API response, and also the calls a worker or cron job makes to outside APIs, and the data an outside client reads from your managed database or key-value store. Every service type in the workspace counts, on every server it runs on.
What does NOT count:
- data coming in to your services
- traffic between your own services inside Voroa (an app reading its own database, for example)
- traffic Voroa itself generates, such as backups and database replication
- files answered from the edge cache, which never reach your service
Bot and attack traffic that your service answers is still outbound data, so it counts.
What each plan includes
Each plan includes a monthly amount of outbound bandwidth, shown on the pricing page. The allowance resets on the 1st of each month (IST).
Extra bandwidth
If your plan lists a price per GB of extra bandwidth, use above the included amount is billed after the month ends, as one “Bandwidth” line on your next monthly invoice, with GST:
- only whole GB are billed, rounded down - a partial GB is never charged
- if you change plan during a month, that month uses the best terms you held during it (the larger allowance and the lower price)
- a month is billed only if the price applied for the whole month
There is no automatic cap on extra bandwidth. Watch the usage page during the month if your traffic is growing quickly.
See your usage by service
Open Billing > Usage in your workspace. The bandwidth meter shows the month’s total against your allowance, a table of how much each service sent (with its share), and, when extra use applies, an estimate of the extra so far.
Keep bandwidth down
The usual surprises are large images served uncompressed, an API returning far more of each record than the client needs, and a monitoring tool polling an endpoint far more often than anyone intended.
- Compress responses. Turn on gzip or Brotli in your framework for HTML, JSON and text.
- Resize and convert images. Serve WebP or AVIF at the size the page shows, not the original upload.
- Cache static files at the edge. Files answered from the edge cache do not count against your allowance.
- Return only the fields you need. Paginate long lists and drop unused fields from API responses.
- Find the noisy service first. The per-service table on Billing > Usage shows which service sends the most, so you fix the right one.
Frequently asked questions
Does traffic from my app to its database count?
No. Traffic between your own services inside Voroa does not count. Only data sent out to the public internet does.
Do uploads to my service count?
No. Incoming data is not counted.
When does the allowance reset?
On the 1st of each month, India time.