Deploy a Next.js app from GitHub in India

This guide shows you how to deploy a Next.js app from a GitHub repository to Voroa — from your first build to a live URL that redeploys on every push. There is no server to provision and no cPanel to set up: connect your repository and Voroa builds and runs your Next.js app, hosted in India and billed in rupees.

Before you start

• A GitHub account with your Next.js repository.
• A build and a start script in package.json. A standard Next.js app already has "build": "next build" and "start": "next start".
• Your app does not need to hard-code a port. next start reads the port Voroa provides, so it is reachable as soon as it starts.

Step 1 — Connect GitHub and create a service

From the dashboard, select Connect GitHub and install Voroa on the repository you want to deploy. Then select New service, pick the repository and branch, and give the service a name.

Step 2 — Confirm your build and start commands

Voroa builds most Next.js apps automatically. If you want to be explicit, set them from your service settings:

• Build command: npm install && npm run build
• Start command: npm run start

See build and start commands for where to set these.

If your repository has a tsconfig.tsbuildinfo file committed to it, add it to your .gitignore and remove it. It is a cache TypeScript writes while it compiles, not part of your source, and it does not belong in version control. Voroa skips it during the build and notes this in your build log, so your deploy will not fail because of it either way.

Step 3 — Set the Node version (optional)

Voroa builds most apps automatically, on the Node version your repository declares; without one, a service keeps the version it was created with (Node 20 for new services). If your app needs a different major version — for example to match a newer Next.js release — declare it in your repository with a .nvmrc or .node-version file, or an engines.node field in package.json. There is nothing to set in the dashboard.

Step 4 — Add environment variables

If your app reads configuration or secrets at build or runtime (an API URL, a database connection string, an auth secret), add them before you deploy. Remember that Next.js inlines any variable prefixed with NEXT_PUBLIC_ into the browser bundle at build time, so it must be present when the build runs. See environment variables for the full flow.

Step 5 — Deploy

Select Deploy. Voroa installs your dependencies, runs the production build, and streams the logs as it goes. When the build finishes, your service gets a live URL you can open right away.

Later builds of the same service reuse its own Next.js build cache, so after the first deploy next build usually runs faster. That cache belongs to your service alone and is never shared with another service.

Step 6 — Ship on every push

Turn on auto-deploy and every push to your branch ships a new build automatically. See how to enable auto-deploy.

Next.js hosting in India, billed in rupees

Voroa runs your Next.js app on infrastructure hosted in India, so requests from your users stay fast and your data stays close to home. Billing is entirely in rupees — no dollar invoices and no forex markup. Every payment comes with a proper GST invoice, so a registered business can claim input tax credit, and you can pay by UPI, an Indian card, or netbanking. Start on the free tier and upgrade when you need more memory or room for a team; managed databases are priced separately, and each one is upgraded from its own page. See pricing.

Next steps

• See how Voroa runs server-rendered apps as web services, and what each size costs.
• Add a custom domain with automatic HTTPS.
• Add a managed database for your app’s data.
• Set environment variables for configuration and secrets.