Instance types and prices: CPU and RAM for every service
Voroa instance types from Free (0.1 CPU, 512 MB) to Pro Ultra (8 CPU, 8 GB), priced in rupees with a GST invoice, and how to pick the right size for a service.
What this covers
An instance type is the amount of memory and processor your service is given while it runs. It matters more than most people expect. Too little memory and your process is killed mid-request, usually under exactly the load you were hoping to handle. Too little processor and every request gets slower at the same time rather than a few failing outright. Choosing well is mostly a question of watching what your service actually uses under real traffic, then sizing a little above the peak rather than the average.
Sizes and prices
Web services and background workers use the same sizes. Prices are per service per month, in rupees, with GST added on the invoice.
| Instance type | CPU | Memory (RAM) | Price per month |
|---|---|---|---|
| Free (Nano) | 0.1 | 512 MB | Free |
| Nano Plus | 0.5 | 512 MB | Rs 149 |
| Starter | 1 | 1 GB | Rs 298 |
| Standard | 1 | 2 GB | Rs 498 |
| Standard Plus | 2 | 2 GB | Rs 598 |
| Pro | 2 | 4 GB | Rs 998 |
| Pro Plus | 4 | 4 GB | Rs 1,198 |
| Pro Max | 4 | 8 GB | Rs 1,998 |
| Pro Ultra | 8 | 8 GB | Rs 2,398 |
Larger sizes, with 16 GB or 24 GB of memory or a custom shape, are set up on request through Contact us on the plan page. CPU is a share of processor cores: 0.5 means half of one core.
The dashboard always shows the current list, on the create page and on each service’s Plan page:
Databases and Key Value have their own sizes. See Voroa Postgres and Key Value.
Choosing a paid instance when you create a service
When paid checkout is open on your account, the create page for a web service, background worker or cron job lets you pick a paid instance size directly. Your service is created right away and starts building; the payment screen opens on the same page. Your first charge is prorated to your billing date and GST is added — the exact amount is shown on the payment screen before you authorise it.
Once the payment is confirmed, the new memory and processor limits are applied to your running service live, without a rebuild or a restart. If you close the payment screen without paying, your service stays on the Free instance and nothing is charged — you can upgrade any time from the service’s Plan page. Purchasing paid instances needs the workspace billing permission; other members can create services on the Free instance and ask a workspace admin to upgrade them.
How to pick a size
- Start small, deploy, and send real traffic to the service.
- Open the service’s Compute page and read memory and CPU for the last 48 hours.
- Pick the size whose memory is comfortably above your peak, not your average. Memory is the usual limit: when a process goes over it, it is stopped and restarted.
- Check again after a launch or a big feature, because usage changes with traffic.
| Signal | Likely fix |
|---|---|
| Restarts with an out-of-memory message in the log | A size with more memory |
| Slow responses while CPU sits near 100% | A size with more processor, or more copies (see scaling) |
| Memory and CPU both low | You may be able to move down a size |
Free and paid sizes
The Free instance is meant for trying things out: a free web service sleeps when it has no traffic and wakes on the next request. A paid size stays on. See free instances and idle sleep.
Frequently asked questions
Are the prices inclusive of GST?
No. The prices above are before GST. GST is added on the invoice, and the exact amount is shown on the payment screen before you pay.
Can I change the instance type later?
Yes. Open the service’s Plan page and pick another size. A paid upgrade applies the new memory and processor limits to the running service once the payment is confirmed, without a rebuild.
How do I know my service needs a bigger size?
Look for restarts with an out-of-memory message in the logs, or CPU near 100% while responses slow down. The service’s Compute page shows memory and CPU for the last 48 hours.
Do web services and background workers cost the same?
Yes. Both use the same instance types at the same prices.