Point Voroa at a repository and a folder, and those files are served on a URL with TLS on it. No build runs and no server process - which is why hosting one costs nothing.
Free to host · no compute size to choose
This is the one thing to know before you start, and it is deliberately not buried in the documentation.
Voroa serves the files in your repository exactly as they are. No build runs. So commit the output your build produces - the dist or build folder - and point the site at it. For plain HTML, CSS and JavaScript there is nothing to do at all: point it at the repository root.
If you want the build to run on every push, deploy the same repository as a web service instead. It installs your dependencies, runs your build and serves the result. That is the right choice for a React, Vite, Next.js or Astro project you would rather not commit the output of - and it is the same repository, the same branch and the same platform, just a different service type.
The compiled output of a React, Vue, Svelte or Vite project. Build it in CI or on your machine, commit the output folder, and Voroa serves it. Use hash routing if the app has routes of its own - see the routing note below.
The output of a static site generator - Astro, Eleventy, Hugo, Jekyll or MkDocs. Generated output is files, and files are what this serves best.
A landing page, a microsite, a coming-soon page, a portfolio. No build tool, no configuration, no server. Point it at the repository root and you are done.
Serve the site here and deploy its API as a web service on the same account. One platform, one region, one bill, and one place to look when something breaks.
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 documentationEvery 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 documentationStatic hosting is free - there is no compute size to choose. A static site still counts against the services your workspace plan allows.
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.
Create your Voroa account. Email and a password, or sign in with GitHub.
Connect GitHub and choose the repository and branch that holds your files.
Set the folder to serve. The repository root, or the output folder your build writes.
Voroa publishes it and gives you the URL.
Add your own domain. The certificate is issued for you.
Push to that branch. The new files go live, and the previous release stays as your rollback.
No. A static site serves the files already in your repository. Commit your built output and point the site at that folder. If you want the build to run for you on every push, deploy the same repository as a web service instead.
Whichever one you choose. The repository root for plain HTML, or the folder your build writes - commonly dist or build. You can change it later and redeploy.
Only for routes reached from inside the app. A static site serves the files that exist, so a visitor who opens /dashboard directly, or refreshes on it, gets a 404 - there is no rule that sends unknown paths back to index.html. Use hash routing, or deploy the project as a Web Service, which runs your own server and can answer every path.
Yes, and the certificate is issued and renewed for you. How many custom domains you get depends on your workspace plan - see pricing.
Yes. The previous release is kept, so you can put it back immediately rather than waiting on another push to finish.
No. There is no application process to write anything, so a disk would have nothing to do.
In Mumbai (IN). Billing is in rupees, and every charge comes with a GST invoice.
You deploy from a Git repository instead of a drag-and-drop upload, and you commit your built folder, because Voroa serves it as it is. We explain the move from drag-and-drop in Netlify Drop and Git deploys, list what the Netlify free plan limits are today, and compare the two in a Netlify alternative for India.
Connect a repository, pick the folder, and it is live on a URL with TLS. Static hosting is free and needs no card.
Free to host, no card needed.