Hostinger vs n8n Cloud: setup, maintenance and total cost compared

Disclosure: Some links to Hostinger on this page are affiliate links. If you buy through them we may earn a commission, at no extra cost to you. It does not change which plan we recommend.
The comparison people make is "₹799 a month versus €20 a month", decide that self-hosting is obviously cheaper, and then spend the next six months learning what the gap actually buys. Sometimes that is a good trade. Often it is not.
This is a straight comparison of running n8n on a Hostinger VPS against paying for n8n Cloud, written for Indian businesses — which means the exchange rate, GST and the cost of your own time all belong in the maths.
What you are actually choosing between
n8n is open source. The Community edition is free, forever, and feature-complete for the thing most people want it for: connecting apps and running workflows. You can put it on any Linux server.
n8n Cloud is the same software, run by the company that makes it, with the operating problems removed — updates, backups, uptime, scaling, SSL, and the parts of the product that are not in the free edition.
So the decision is not really about features. It is about who carries the operational burden, and about one specific number: executions.
The prices, honestly converted
n8n Cloud prices in euros. At roughly ₹110 to the euro, and allowing for the 2–3% forex markup most Indian credit cards add on international transactions, the real monthly cost looks like this:
| Option | Headline price | Realistic ₹/month | Executions included |
|---|---|---|---|
| n8n Cloud Starter | €20/mo (annual) | ≈ ₹2,250 | 2,500 |
| n8n Cloud Pro | €50/mo (annual) | ≈ ₹5,650 | 10,000 |
| Hostinger KVM 1 | ₹599/mo (24 mo) | ₹599 → ₹999 at renewal | Unlimited |
| Hostinger KVM 2 | ₹799/mo (24 mo) | ₹799 → ₹1,199 at renewal | Unlimited |
Two India-specific notes that pricing pages do not mention. If you are GST-registered, a foreign software subscription normally means self-assessing 18% IGST under reverse charge and reclaiming it — the same reverse-charge mechanic that applies to most foreign software subscriptions. And a ₹799 domestic invoice from Hostinger India is a far easier thing to put through your books than a euro card charge.
The number that actually decides it: executions
Everything else in this comparison is noise next to this. n8n Cloud charges by workflow executions — one run of one workflow counts as one execution, no matter how many steps are inside it. Self-hosting has no such limit; you are limited only by what the server can physically do.
That makes the decision almost arithmetic:
- Under ~2,500 executions a month — a few scheduled jobs, form submissions, CRM syncs. Cloud Starter is comfortable and self-hosting saves you about ₹1,450 a month for a server you now have to run.
- 2,500 to 10,000 — Cloud Pro at ≈₹5,650 against ₹799 for a VPS. The gap is now about ₹4,850 a month, or ₹58,000 a year. That is real money, and this is where most Indian teams move.
- Above 10,000 — if you poll an API every five minutes you have already used 8,640 executions on a single workflow. At this volume Cloud economics stop making sense for anything except the enterprise tiers, and self-hosting is the obvious answer.
Count your likely executions before anything else. A single "check this inbox every minute" trigger is 43,200 executions a month on its own.
What self-hosting costs in time
This is the part that gets left out, so here it is in full.
Setup
Hostinger ships a one-click n8n template for its VPS plans — it provisions Ubuntu, installs n8n and its dependencies and gets you to a login screen. Realistically, 20 minutes to a working instance, plus another 30–60 minutes to point a subdomain at it, issue SSL, set a strong admin password and lock down SSH. Call it two hours for someone who has done it before and half a day for someone who has not.
Ongoing
- Updates. n8n ships frequently. You decide when to pull a new version, and occasionally a node changes behaviour and a workflow breaks. Budget an hour a month.
- Backups. Hostinger includes weekly backups and snapshots on the VPS plans, which covers the server. It does not cover "someone edited a workflow wrong on Tuesday" — for that you want your workflows exported to Git.
- Monitoring. If n8n stops at 3am, nothing tells you. Cloud tells you. You will want an uptime check and an alert.
- Debugging. When something breaks, there is no support ticket. There is a community forum and your own logs.
Put a conservative two hours a month against that. At even ₹500 an hour of your own time, self-hosting's ₹799 becomes ₹1,799 — still well under Cloud Pro, and still well above Cloud Starter. That is the honest shape of it.
Self-hosting is not free. It is cheap, and it is paid for in attention rather than rupees.
What you give up on the Community edition
The free self-hosted edition does not include everything. The notable omissions are SSO and LDAP, external secret stores, Git-based version control for workflows, queue mode for horizontal scaling, log streaming, extended execution-data retention, and any form of paid support.
For a two-person team, none of that matters. For an agency with staff turnover handling client credentials, "no SSO and no external secret store" is a genuine governance problem worth thinking about before you commit.
Where your clients' data sits
This argument is under-used and often the one that actually closes the decision. On a VPS, every lead record, phone number and invoice that passes through a workflow stays on a server you control, in a region you chose. Hostinger has a Mumbai data centre, so an Indian business can keep Indian customer data in India without any special arrangement.
If you handle health, financial or education data — the sectors where we see the most scrutiny, and where a client's legal team reads the data-processing questions carefully — being able to answer "it is on our own server in Mumbai" is worth more than ₹800 a month. It is the same reasoning behind keeping analytics and tracking first-party rather than handing everything to third-party scripts — and the same instinct behind the privacy extensions people install for their own browsing.
When n8n Cloud is the right answer
- You are testing whether automation helps at all, and want to find out this week.
- Nobody on the team is comfortable in a Linux terminal, and nobody wants to be.
- Your volume is genuinely low — under 2,500 executions a month and unlikely to grow fast.
- You need SSO, audit logs or formal support for compliance reasons.
- An automation going down for six hours would cost you more than the subscription does in a year.
When a Hostinger VPS is the right answer
- You will cross 2,500 executions a month — which happens faster than people expect.
- You want unlimited workflows and triggers without watching a meter.
- Data residency matters to you or your clients.
- You already run something on a server, or you have someone who does.
- You want the box to do more than n8n — a staging site, a dashboard, a scraper. The KVM 2 vs KVM 4 comparison covers how much headroom each plan leaves for that.
The sensible path for most businesses
Start on n8n Cloud's trial or Starter plan. Build the three workflows you think you need. Run them for a month and look at two numbers: executions used, and how many of those workflows you still care about.
Most people find that two of the three were a bad idea and the third is now critical. At that point you know your real volume, you know the workflows are worth hosting, and moving is easy: workflows export as JSON and import into a fresh instance in minutes. Credentials have to be re-entered by hand — which is a security feature, not a bug.
That order — prove it, then own it — avoids both failure modes: paying a subscription for workflows nobody uses, and spending a weekend configuring a server for an automation you abandon in March.
The question people forget to ask
Before either option, ask what happens when an automation fails silently. Not loudly — silently. A workflow that stops firing is far more expensive than one that throws an error, because nobody notices for three weeks and by then you have lost three weeks of leads.
n8n Cloud will keep the instance alive but it will not tell you that a workflow stopped producing useful output. Self-hosting will not tell you either. In both cases the answer is the same: build one workflow whose only job is to check that the others ran, and send yourself a message when they did not. It takes an hour and it is the difference between automation you can trust and automation you have to keep checking — which defeats the point.
Our verdict
For an Indian business past the experimenting stage, self-hosting on KVM 2 is the better economic answer by a wide margin, and the one we end up recommending most often. For a team that genuinely cannot afford an hour of downtime and has nobody to own a server, Cloud is worth every euro.
What you should not do is pick self-hosting purely on the ₹799 headline and then leave it unmonitored and three versions out of date. That is the version of this decision that costs money.
If you are sizing the server next, the KVM 2 vs KVM 4 comparison is the companion to this one. And for the day-to-day of building workflows, a JSON viewer from the developer extensions category saves opening another tab, while the best AI extensions cover the browser side of the same job.
Frequently asked questions
Is self-hosted n8n really free?
The software is free and open source. The hosting is not — about ₹799 a month for a VPS that comfortably runs it — and neither is your time. Budget roughly two hours a month for updates, backups and the occasional broken workflow. Self-hosting is cheap, not free.
How many executions do I get with self-hosted n8n?
There is no limit. You are constrained only by what the server can physically process. That is the single biggest difference from n8n Cloud, which includes 2,500 executions on Starter and 10,000 on Pro, and it is why high-frequency triggers push people towards self-hosting fast.
Can I move from n8n Cloud to a self-hosted instance later?
Yes. Workflows export as JSON and import into a fresh instance in minutes. Credentials have to be re-entered by hand, which is a security design rather than an obstacle. Proving the workflows on Cloud first and moving once they matter is the path we usually recommend.
Does self-hosting n8n keep data in India?
It can. Hostinger has a Mumbai data centre, so choosing it at setup keeps every record your workflows touch on a server in India. For businesses handling health, financial or education data, that is often the argument that decides the whole comparison.
