DigitalOcean vs Hostinger for n8n — and Whether to Self-Host at All
Before choosing a host, settle the question underneath it: should you self-host n8n at all?
The answer is unusually clear, because the self-hosted Community Edition is free software with unlimited executions. You pay only for the server. So the break-even against n8n Cloud isn’t a gradual curve — it arrives almost immediately and then widens.
Self-hosted vs n8n Cloud
n8n Cloud prices by execution volume:
| Cloud plan | Executions/month | Price (annual billing) |
|---|---|---|
| Starter | 2,500 | €20 (~$22) |
| Pro | 10,000 | €50 (~$54) |
| Business | 40,000 | €800 (~$864) |
Against a self-hosted instance with unlimited executions:
| Your volume | Cloud tier needed | Cloud cost | Self-hosted on Hostinger |
|---|---|---|---|
| 1,000 | Starter | ~$22 | ~$15 |
| 10,000 | Pro | ~$54 | ~$15 |
| 40,000 | Business | ~$864 | ~$15 |
Two things worth noticing.
The Business tier costs about €0.02 per execution against Pro’s €0.005 — four times more. You aren’t buying throughput at that tier, you’re buying SSO, shared projects, Git version control and support. Judging it on execution count alone is unfair; judging your bill on it is entirely fair.
And self-hosting wins on price at essentially every volume, because the server cost is fixed while Cloud’s is per-execution. What Cloud sells is not having to run it — no upgrades, no database, no backups, no 3am restarts. That’s a real product and for some teams it’s worth €800 a month.
Self-host if you have the operational appetite, your volume is meaningful, or you need unlimited executions on a budget. Use Cloud if your automations are business-critical and nobody on the team wants to own a Postgres instance.
If you self-host, the rest of this article is about where.
The architectural difference that matters
This is the actual distinction between these two providers, and it isn’t price.
Hostinger gives you a one-click n8n template on a single box. n8n, its database, and everything else run on the same VPS. It’s the fastest route from nothing to a working instance — a few clicks rather than a shell session — and the cheapest.
DigitalOcean gives you a Marketplace n8n image plus the option of a managed database alongside it. Postgres runs as a separate managed service with its own backups, failover and patching, rather than as a container on the same machine.
That difference decides what happens on your worst day. If your single box dies with Postgres on it, your workflow history, credentials and execution data die with it unless your backups were working. A managed database survives the instance entirely — you rebuild the VPS, point it at the database, and carry on.
The cost of that resilience is real: DigitalOcean’s 8 GB Basic Droplet is $48/month against Hostinger’s KVM 2 at $8.79 introductory and $14.99 at renewal, and a managed database is a further separate line item on top.
So the honest framing is: Hostinger is roughly a quarter of the price for a setup where the database is your problem. DigitalOcean costs multiples more for one where it isn’t.
Which to choose
Hostinger if you’re self-hosting n8n for yourself or a small team, your workflows are valuable but not existential, and you’re willing to verify that backups actually work. The one-click template, weekly backups, browser terminal and 8 GB at the KVM 2 tier make it the fastest and cheapest credible path. Two caveats: KVM 2 gives 2 vCPUs where competitors give 4 at that memory, and the price rises 71% at renewal.
DigitalOcean if your automations are business-critical, you want Postgres managed separately, you’ll deploy from the API or Terraform, or you’re already running infrastructure there. You’ll pay several times more, and what you’re buying is durability and platform rather than n8n specifically.
Neither if you only need a couple of thousand executions a month and nobody wants to be on call. That’s n8n Cloud Starter at ~$22, and it’s a defensible purchase.
Sizing it properly
Whichever you pick, the sizing rules are the same and are covered in depth in our n8n VPS guide:
- Regular mode runs everything in one process. Fine for modest workflows.
- Queue mode splits the main process from workers, which is how you scale — and each worker carries its own memory, so it’s the reason 4 GB stops being enough.
- Postgres over SQLite for anything you rely on. SQLite is fine for a test instance and a liability under concurrency.
- Execution data is what fills your disk. n8n stores the payload of every execution by default. Prune it, or your disk fills silently — the single most common self-hosted n8n failure.
At 8 GB you have room for queue mode with a couple of workers plus Postgres on the same box. Below 4 GB, queue mode isn’t realistic.
The operational part nobody writes about
What happens to in-flight executions when you resize the instance?
Resizing a VPS means a reboot. Any execution running at that moment is interrupted, and what happens next depends entirely on your configuration:
- In regular mode, an interrupted execution is simply lost. There’s no worker to retry it and no queue holding it.
- In queue mode, jobs sit in Redis. Workers that die mid-job can have their work re-queued, so an interrupted execution has a path back — which is a large part of why queue mode is worth the extra memory.
- Executions triggered by webhooks are the fragile case either way. If n8n isn’t listening when the webhook fires, the caller gets an error and the event is gone unless the sender retries.
Practical sequence before any resize or upgrade: stop accepting new work, let in-flight executions drain, snapshot, then resize. On Hostinger take the free snapshot first — remembering it’s a single snapshot that overwrites and expires after 20 days, so it’s a checkpoint rather than a backup. On DigitalOcean enable backups explicitly, because they’re off by default and cost 20–30% extra.
And whichever host you’re on, test a restore before you need one. A backup you’ve never restored is a hypothesis.
Where to buy
Check Hostinger VPS pricing → · Read our Hostinger review
Our DigitalOcean tracking link is currently out of action, so there’s no tracked link for it here — our DigitalOcean expert review covers the platform in detail.
How we picked
n8n Cloud pricing is from published 2026 plan documentation: Starter at €20/month annually for 2,500 executions, Pro at €50 for 10,000, Business at €800 for 40,000, with roughly 17% saved on annual billing. The Community Edition’s unlimited executions are a property of the self-hosted software.
Provider pricing comes from each vendor’s pages, verified August 2026 — DigitalOcean’s 8 GB Basic Droplet at $48 and Hostinger’s KVM 2 at $8.79 introductory, $14.99 at renewal. Euro conversions are approximate at $1.08.
We have not benchmarked n8n throughput on either provider. Execution capacity depends far more on what your workflows do — an HTTP request against an API is not comparable to a workflow processing large payloads — than on which of these hosts runs it. The sizing guidance above is based on n8n’s architecture rather than our measurements.
This page carries one affiliate link, to Hostinger, which is also the cheaper of the two options compared.
FAQ
Is self-hosting n8n cheaper than n8n Cloud?
Almost always. The Community Edition is free with unlimited executions, so you pay only for the server — roughly $15/month for a capable VPS against €20 for Cloud’s 2,500-execution Starter tier or €800 for the 40,000-execution Business tier. What Cloud sells is not having to operate it.
How many executions does self-hosted n8n allow?
Unlimited — the constraint is your server’s CPU, memory and disk rather than a licence. That’s the structural difference from Cloud, which meters executions per plan.
Should I run Postgres on the same server as n8n?
For a personal or small-team instance, yes — it’s simpler and cheaper. For anything business-critical, a managed database separate from the VPS means your workflow history and credentials survive the instance failing, which is the main architectural argument for DigitalOcean over Hostinger here.
What happens to running workflows when I resize my VPS?
They’re interrupted by the reboot. In regular mode an in-flight execution is lost; in queue mode jobs held in Redis can be re-queued to another worker. Webhook-triggered executions are fragile either way, since the event is gone if n8n isn’t listening. Drain in-flight work and snapshot before resizing.
Which Hostinger plan do I need for n8n?
KVM 2 with 8 GB is the sensible floor if you want queue mode with a couple of workers plus Postgres on the same box. KVM 1’s 4 GB runs a single-process instance but leaves little room to scale. Our Hostinger plan guide works through the tiers.
Why does my self-hosted n8n keep filling the disk?
n8n saves the data of every execution by default, and on a busy instance that grows quickly. Configure execution-data pruning and set a retention window — it’s the most common reason a self-hosted n8n box runs out of space.
Related Products
