Hosting for startups in India: what to pick at each stage
Hosting for startups in India: shared hosting, VPS, PaaS or AWS at each stage, and the early choices (data location, billing, GST) that are costly to undo.
Most hosting decisions are reversible. A few are not, and they tend to be the ones made casually at the start — when the priority is getting something live and none of the downstream constraints exist yet.
This page maps the stages an Indian software business actually passes through and flags which choices get expensive to undo. The tax points are general information, not tax advice — confirm your own registration and treatment with your accountant.
Shared hosting, VPS, PaaS or a hyperscaler?
The four kinds of hosting an Indian startup usually compares solve different problems. Pick by what you are running and who will look after it, not by the cheapest monthly price.
| Option | Good for | What you take on |
|---|---|---|
| Shared hosting (cPanel) | A WordPress or PHP marketing site | Cannot run a Node.js or Python server, background jobs or your own database setup |
| A VPS | A team that wants full control of a Linux box | Patching, firewall, TLS, backups, monitoring and restarts are all yours |
| A PaaS such as Voroa | Apps deployed from a GitHub repository, plus a managed database | Less low-level control; you work within the platform’s runtimes and limits |
| AWS, Google Cloud or Azure | Large or regulated workloads with a dedicated DevOps person | Many separate services to wire up, and a dollar bill with reverse-charge GST paperwork |
A common path is to start on a PaaS, because it removes server work while the team is small, and to move parts to a hyperscaler only when a specific need appears.
Stage 1: side project, no entity
You are the only user who matters. Nothing is registered, there is no invoice to keep, and the only real requirement is that deploying is fast enough that you keep doing it.
What matters: deploy from a git push without a build pipeline to maintain. Free or near-free.
What does not matter yet: tax treatment, uptime guarantees, backups of data that does not exist.
The one thing worth doing anyway: keep your configuration in environment variables rather than committed to the repository. Not for compliance — because pulling secrets back out of git history later is genuinely unpleasant.
On Voroa every push becomes a deploy you can read back later, with its commit, status and duration:
Stage 2: incorporated, first revenue
This is the stage where hosting stops being a personal expense and starts being a business input, and three things change at once.
Your spend becomes a claimable cost. Once registered for GST, the 18% on hosting is credit rather than cost — but only against a proper tax invoice carrying your GSTIN. Add your GSTIN to billing details before your first payment, because an invoice already issued to the wrong details stays that way. See Do you need a GST number to buy cloud hosting?.
Payment moves from a card to a mandate. Ad-hoc card payments become a recurring bill. In India that means a mandate with a per-debit ceiling, and mandates expire. See UPI AutoPay for cloud hosting.
Downtime starts costing money. Backups become real rather than theoretical, and “it restarts if I notice” stops being an operating model.
The expensive-to-reverse decision here is the currency and jurisdiction of your provider. Migrating a running production application between hosts is a project. Choosing a dollar-billed foreign provider now means either living with the reverse charge compliance and the exchange drift, or doing that migration later under time pressure. See Cloud hosting priced in rupees versus dollars.
Stage 3: a team
More than one person deploys, which means access is now a question. Shared credentials stop being acceptable roughly the moment the second person joins, and definitely the moment the first person leaves.
What matters: environment variables shared across services rather than copied by hand, and a deploy history you can read back when something breaks. See environment groups and deploy history.
Give each person their own login. On Voroa, paid workspace plans let you invite teammates by email and give each one a role, so nobody shares a password and you can remove one person without touching anyone else. See team members and roles, and turn on two-step verification for every account that can deploy.
Stage 4: first enterprise customer
Someone sends you a security questionnaire. It asks where data is stored, whether it leaves the country, how backups work, and how secrets are handled.
This is where jurisdiction stops being a preference and becomes a sales blocker. “Our data is in India” is a one-line answer. “Our data is in a region of a foreign provider, and here is our cross-border transfer position” is a conversation with their legal team.
See Where your app and database actually run for the facts most questionnaires ask for.
The decisions worth making early
Ranked by how painful they are to reverse:
- Where your data lives. Hardest to change. Decide it before you have production data and enterprise customers, not after.
- Who your provider bills, and in what currency. Determines your monthly compliance work for as long as you stay.
- Secrets out of the repository. Cheap now, tedious later.
- Named access rather than shared logins. Cheap now, a security incident later.
Everything else — instance size, database plan, custom domains, adding services — is genuinely changeable when you need it, and is not worth optimising in advance.
Where Voroa fits
Voroa covers the first two stages well: you deploy from a GitHub repository, everything runs in India, and billing is in rupees with a GST invoice. There is a free tier for stage one.
It also covers most of stage three: per-person team accounts with roles, two-step verification, and audit logs of who changed what (on the Growth, Scale and Custom plans).
Be clear-eyed about stage four. Some items on an enterprise questionnaire, such as single sign-on (SSO) and a published penetration-testing policy, are not available on Voroa today. What Voroa can answer is the data-residency question, the access and audit questions, and billing that an Indian finance team does not have to work around. If your blocker is SSO, ask before you migrate.
See pricing, what is Voroa, and the two pieces most startups start with: a web service for the app and a managed Postgres database.
Moving from a dollar-billed host? You can apply for migration credits: up to Rs 10,000 set against your Voroa bills, granted by hand after a person reads your application.
Frequently asked questions
Is shared hosting enough for a startup?
For a marketing website, often yes. For a product, usually not: shared hosting cannot run a long-lived Node.js or Python server, background workers or scheduled jobs. Most software startups outgrow it with their first real app.
Should an Indian startup start on AWS?
Only if you have someone to run it. AWS is powerful but has many moving parts, bills in dollars, and brings reverse-charge GST paperwork. A PaaS gets a small team live faster, and you can move a part to AWS later when there is a clear reason. See reverse charge on foreign cloud hosting.
Can a startup claim GST back on hosting?
Yes, if it is GST-registered and the invoice carries its GSTIN. The 18% then becomes input tax credit instead of a cost. See GST input tax credit on cloud hosting.
Is there a free tier to start with?
Yes. Voroa’s Free plan needs no credit card and covers small services and one database. See free instances.