We already have an article comparing self-hosted n8n with n8n Cloud, covering the policy and feature differences: per-execution billing, where your data goes, community nodes.
This one skips all of that and covers exactly one thing: money. And specifically the kind of arithmetic that counts time as money too.
30-second overview
| Item | Self-hosted | Managed |
|---|---|---|
| Monthly cost (including time) | NT$1,030–1,730 | avg. NT$499/mo (billed yearly) |
| Biggest cost item | Your maintenance time | A fixed subscription fee (billed yearly) |
| When self-hosting wins | You already have a server and n8n is service number N | — |
| When managed wins | — | n8n is your first self-hosted service |
| Not counted here | What it costs when a workflow breaks at 2 a.m. and you find out the next day | |
Why an hourly rate has to be in the cost table
The most common mistake when comparing self-hosted with managed is putting "VPS monthly fee" up against "managed monthly fee" and concluding that self-hosting is cheaper. That comparison doesn't hold, because it assumes your time is free.
If you're a freelancer or an employee, your time has a clear opportunity cost. Two hours spent on an n8n upgrade is two hours not spent on billable work. The figures below use NT$600/hour as the conversion rate; substitute your own number and redo the math.
The full cost of self-hosting n8n
| Item | Amount/month | Notes |
|---|---|---|
| VPS | NT$200–400 | n8n itself is light; 1 GB of memory is usually enough |
| Domain (if needed) | About NT$30 | Annual fee amortized |
| Initial setup, amortized | NT$100–300 | 2–5 hours, spread over 12 months |
| Version upgrades | NT$300–600 | About 0.5–1 hour a month |
| Backups and verification | NT$300 | About 0.5 hours a month |
| SSL renewals and odds and ends | NT$100 | Mostly automatable, but still needs an occasional check |
| Total | NT$1,030–1,730 | Assuming everything runs smoothly |
Compare that with managed n8n on RoamerHost: NT$5,988 billed yearly, avg. NT$499/mo (1 CPU core / 2 GB storage), including SSL, a dedicated subdomain, backups and version maintenance.
But that table isn't entirely fair to self-hosting
To be honest about it: there are two ways the table above is unfair to self-hosting, and you should know about them.
First, one VPS can run more than one service. If your machine is already running other things, the marginal server cost of n8n is close to zero, and the cost of self-hosting drops sharply.
Second, operations have economies of scale. Managing one n8n instance takes an hour; managing five services does not take five hours. If you already run other self-hosted services, the marginal time cost of adding n8n is very low.
So where's the break-even point?
Putting those two points together, a fairly clear rule of thumb falls out:
| Your situation | Recommendation |
|---|---|
| No existing server; n8n is your first self-hosted service | Managed — all the fixed costs of self-hosting get absorbed by this one service, which doesn't pay off |
| You have a server and an ops routine; n8n is service number N | Self-hosted — the marginal cost is low, so it's worth it |
| Your time is expensive, or n8n runs business-critical workflows | Managed — what you're buying is not having to deal with it |
| You want to learn Docker and server operations | Self-hosted — here the time cost is tuition, not a loss |
An overlooked variable: what a broken workflow costs
n8n usually isn't a toy. What it runs tends to be order syncing, customer notifications, data backups — workflows where a failure gets noticed.
When you self-host and the service dies at 2 a.m., your automation stops and you don't find out until the next morning. The cost of that risk can't go in a table, but it should be in your head when you decide.
Another way to look at it: what does the money buy?
Set the numbers aside and the real difference between self-hosting and managed comes down to one sentence: when something breaks, whose evening is it?
Self-hosting has a lower monthly cost because you kept the operations work for yourself. That work isn't free; it just hasn't been invoiced yet. The bill arrives the day a version upgrade breaks compatibility, the day a certificate expires, the day the disk fills up.
Managed costs more per month because those evenings have been bought from you. Whether that's worth it depends on what your evenings are worth and how much you hate dealing with this kind of thing. Only you can answer those two questions, and no cost table can compute them.
FAQ
Q: A VPS is two or three hundred a month — how did this come to over a thousand?
Because your time is in the total. Installation, domain and SSL setup, version upgrades, backup verification: in a good month that's about one to two hours. At NT$600/hour, the time cost exceeds the server rent.
Q: One VPS can run lots of services — doesn't that make it a bargain?
Yes, and that's the most genuine advantage of self-hosting; the article says so too. If n8n is the fifth service on your machine, the marginal cost is close to zero. What doesn't pay off is keeping a machine and an ops routine alive for n8n alone.
Q: Does managed hosting cap executions?
No. Managed is billed per instance, and executions aren't counted separately. What you do need to watch is resources, and the fact that execution logs accumulate and take up space — see execution data growth.
Q: I just want to learn Docker — is self-hosting better for that?
Yes. In that case the time cost is tuition, not a loss. The math in this article doesn't apply to people whose goal is learning.
Q: How do you price a broken workflow?
You can't put it in a table. But what n8n runs tends to be order syncing and customer notifications — workflows where a failure gets noticed — and if you self-host and the service dies at 2 a.m., you don't find out until the next morning. That risk belongs in your decision even though you can't put a number on it.
A practical decision sequence
Rather than calculating to the last decimal, work through these three questions in order:
- Do you already have a machine that runs things and that you already maintain? If not, all the fixed costs of self-hosting get absorbed by this one service — go managed.
- Will n8n run business-critical workflows? If so, factor in the cost of it dying overnight; that's usually bigger than the difference in monthly fees.
- Do you want to learn this stack? If yes, self-host — that time is tuition.
Three answers usually produce a conclusion, without actually pricing out every line item. The value of a cost table is showing you which items get overlooked, not getting you to the exact dollar.
Sources and further links
n8n's nodes and pricing change often; these are the primary sources to verify against:
- n8n official documentation
- n8n official pricing — cloud plans and quotas
- n8n source code and release history — the authoritative source for license terms
Further reading
- Moving from Zapier to n8n: why you can't just copy your workflows over
- Self-hosted n8n vs. n8n Cloud: data sovereignty, executions and cost
- n8n vs. Zapier vs. Make: monthly cost and data residency for teams in Taiwan
- What is n8n? An introduction to the workflow automation platform
- RoamerHost managed n8n plans
Want someone to build it for you?
If you'd rather not assemble these workflows yourself, or the scale is big enough that you want someone planning it with you, Roamer Tech (RoamerHost's parent company) takes on contract work in business process automation and AI agents:
