Node.js and TypeScript API hosting
Express, Fastify, NestJS or a plain HTTP server. Voroa detects Node, installs, builds, and starts your process. Read the port from the environment and there is nothing else to configure. More on Node.js hosting.
Services
Web Services. Hosted in India.
Deploy an app or API from a GitHub repository. Voroa installs, builds and runs it on a size you pick, and repeats that on every push without dropping a request.
Free size included · Paid sizes from ₹298/mo
- Voroa builds it
- No-downtime deploys
- Scale when needed
- 2,000+Developers
- 24,100+Deploys
- MumbaiWhere your app runs
What every web service comes with
- A URL with TLS, from the first deploy
- A new release on every push to your branch
- Releases that start before the old one stops
- One-click rollback to the previous release
- Your own domains, with certificates handled
- Build and runtime logs you can read
- Environment variables and shared env groups
- One bill, in rupees, with a GST invoice
- Runs in Mumbai (IN)
Node.js, Python and Docker apps, deployed from GitHub
If it listens for HTTP and lives in a Git repository, it belongs here.
Server-rendered frameworks
Next.js, Nuxt, Remix, SvelteKit and Astro in server mode. The build runs on every push, so the page a visitor gets is built from the commit you pushed.
Python and Django hosting
Django, FastAPI or Flask behind the server of your choice. Set your own start command when the default is not what you want, and change it later without recreating the service. More on Python hosting.
Docker hosting, from your own Dockerfile
Choose Docker as the runtime and Voroa builds from your Dockerfile instead of detecting the stack, so the image you run here is the image you tested. Pick it when you create the service.
What a web service usually works with
Most apps need somewhere to keep data and somewhere to do slow work. Keep your data in managed PostgreSQL, put sessions and cache in a Redis-compatible key value store, and move jobs that should not hold up a request to a background worker. A database or store connects through one environment variable, and everything is on one bill, in rupees.
From your repository
Deploy straight from GitHub
Connect a repository, pick a branch, and Voroa builds and runs your app. Most projects need zero configuration. When you do need control, set your own build and start commands, root directory and Node version - and change them any time.
View documentationAuto-deploy
Ship on every push
Turn on auto-deploy and every push to your branch triggers a fresh build and rolls the change out. Your live service always matches your latest commit, and every deploy is recorded with the commit that caused it.
View documentationConfiguration
Secrets go in, and never come back out
Store the configuration your app needs as environment variables, applied to both your builds and your running service. Values are encrypted at rest and are never displayed again - not to you, not to anyone. You can replace a value; nobody can read it back.
View documentationDomains and TLS
Your own domain, with HTTPS handled
Every service gets a live HTTPS URL the moment it deploys. Point your own domain at it and Voroa issues and renews the certificate for you - nothing to buy, nothing to remember, no expired certificate taking your site down.
View documentationLogs
Watch the build, then read the runtime
Your build streams line by line as it runs, and your running service keeps its own runtime logs - so when something misbehaves in production you read what happened instead of guessing. Every deploy keeps its status and its commit.
View documentationSizing, and what it costs
A service runs on a size you pick, and you change it when the app asks you to. Start on the free size while you are still building; move up when real traffic arrives.
Web services
per serviceStart free, move up a size when the service needs it. Every size is billed per service, per month.
- Deploys from your GitHub repo
- A live HTTPS URL with managed TLS
- Runtime logs and full deploy history
- Custom domains
| Plan | CPU / RAM / Storage | Price | Action |
|---|---|---|---|
Nanonano |
0.1 CPU · 512 MB RAM | ₹0/month+18% GST | Get started |
Starterstarter |
1 CPU · 1 GB RAM | ₹298/month+18% GST | Get started |
Standardstandard |
1 CPU · 2 GB RAM | ₹498/month+18% GST | Get started |
Standard Plusstandard_plus |
2 CPU · 2 GB RAM | ₹598/month+18% GST | Get started |
Propro |
2 CPU · 4 GB RAM | ₹998/month+18% GST | Get started |
Pro Pluspro_plus |
4 CPU · 4 GB RAM | ₹1,198/month+18% GST | Get started |
Pro Maxpro_max |
4 CPU · 8 GB RAM | ₹1,998/month+18% GST | Get started |
Pro Ultrapro_ultra |
8 CPU · 8 GB RAM | ₹2,398/month+18% GST | Get started |
Scalescale |
8 CPU · 16 GB RAM | CustomPriced to your workload | Talk to us |
Scale Maxscale_max |
8 CPU · 24 GB RAM | CustomPriced to your workload | Talk to us |
Your bill is one workspace plan plus a compute size for each service you run; the pricing page lists the workspace plans. All prices in INR and exclude 18% GST; a GST tax invoice is issued on every payment. No foreign currency payments, no forex markup.
How it works
From a repository to a live URL
- 01
Create your Voroa account. Email and a password, or sign in with GitHub.
- 02
Connect GitHub and choose the repository and branch you want deployed.
- 03
Pick a size. The free size costs nothing and needs no card.
- 04
Voroa installs, builds and starts your service, then gives you its URL.
- 05
Add your own domain when you are ready. The certificate is issued for you.
- 06
Push to that branch. Every push is a new release, and the previous one stays as your rollback.
Billing
One rupee bill, itemised, with GST
Your services and every database beside them land on a single monthly invoice, paid over UPI-Autopay or an Indian card. Each line names what it is for, and the tax is split out the way your accountant needs it for input tax credit.
View documentationDo I have to write a Dockerfile?
No. Voroa detects common stacks and builds them without one. If you do have a Dockerfile and want it used, choose Docker as the runtime when you create the service - Voroa does not switch to it on its own, and the runtime cannot be changed afterwards.
Which port should my app listen on?
Read the port from the environment and bind to it - that is the one thing that can never go wrong. If your app instead listens on a single other port, Voroa finds it and routes there rather than failing your deploy.
Can I set my own build and start commands?
Yes. Build command, start command, pre-deploy command and root directory are all yours to set, and you can change any of them later and redeploy.
Is there downtime when I deploy?
The new release is started and checked before the old one is stopped, so a normal deploy does not drop requests. A rollback does the same thing in reverse.
Can I run more than one instance of a service?
Yes, once the service is on a paid size. Each extra copy is billed at that size's monthly price, and you see the amount before you confirm. How many copies a service may run is set by your workspace plan, not by the size - see pricing. You choose the number; Voroa does not change it on its own.
Where does it run, and how am I billed?
In Mumbai (IN). Billing is in rupees, and every charge comes with a GST invoice you can hand to your accountant.
Can my frontend stay on Netlify while the API runs here?
Yes. Keep the site where it is and point it at a web service in Mumbai, next to its database. Running a backend alongside Netlify covers what Netlify's own server options do and do not run, and Netlify vs Vercel compares the two frontend hosts for Indian teams.
Deploy something today
Connect a repository, pick the free size, and see your app on a URL. Move up a size when it starts earning its keep.
Free size, no card needed.