"n8n is free, I'll put it on a cheap VPS" is the sentence that starts most self-hosting stories, and it is true as far as it goes. The software costs nothing and a small server costs a few dollars a month. What the sentence leaves out is everything that happens after the install, which is where the real cost of self-hosting lives. This guide lays that out honestly, puts a managed instance beside it, and ends with a way to choose that does not depend on which one we sell.
What self-hosting involves
A VPS provider's one-click n8n template, or a Docker Compose file copied from the docs, gets you a running instance in an afternoon. Then the list begins:
- A domain and a certificate. n8n needs HTTPS for webhooks and OAuth connections. A reverse proxy, a certificate from Let's Encrypt, and a renewal that must keep working.
- A database. The default SQLite file is fine for a test and a liability for production; Postgres is the recommendation, which means running and backing up Postgres.
- Updates. n8n releases often. Each update is a container pull and a restart, and occasionally a breaking change that needs a migration or a workflow fix. Skip updates and you run known vulnerabilities; apply them blindly and you break a workflow at 2 am.
- Backups. Workflows and credentials live in the database. If the disk dies or an update corrupts something, the backup is the business. Someone has to set it up, test a restore, and keep it off the same machine.
- Security. n8n ships without authentication enforced on some setups, a fact its own install guides warn about. The server also needs a firewall, SSH hardening and someone reading the security advisories.
- Resources. A workflow that handles a webhook burst or a large AI step can exhaust a small VPS. Someone notices when the instance stops answering, and that someone is you.
- The night it goes down. Not if. The disk fills, the certificate lapses, the provider reboots the host. Whoever owns the server gets the message, whenever it arrives.
None of this is hard for a person who runs servers for a living. All of it is a second job for a person who does not.
What a managed instance involves
A managed instance is the same self-hosted n8n, with the list above done by the operator. On RinooSol's plans that means a private container with its own database schema and credentials, a subdomain with SSL issued and renewed, updates applied, backups taken on a schedule, automated monitoring, and a person on WhatsApp when something needs one. The instance is live under a minute after payment, in Egyptian pounds.
What you still do: build your workflows, keep your own app credentials in order, and choose a plan big enough for your executions. What you give up: root access to the machine, and the freedom to run anything else on it.
The cost, side by side
The money is the smaller part. Put a number on the time too, at whatever an hour of yours or an engineer's costs.
| Self-hosted VPS | Managed instance | |
|---|---|---|
| Software | Free | Free (included) |
| Server | A few dollars a month for a small VPS, more as workflows grow | Included in the plan |
| Setup | An afternoon, longer the first time | Under a minute |
| Updates and backups | Your hours, every month, forever | Included |
| Monitoring and incidents | Your attention, at any hour | Included, automated |
| Support | Community forum | A person, in Arabic or English |
| Control | Full root access | The instance, not the machine |
| Billing | Provider's currency, usually USD by card | Egyptian pounds, card or WhatsApp |
A reasonable estimate for a competently run self-hosted instance is two to four hours a month of attention, plus a few hours whenever something breaks. Multiply by what that time is worth to you, add the server, and compare it to the managed plan you would need. For most freelancers and small companies the managed plan wins on money before you count the nights.
When self-hosting is right
- You already run servers, or you are learning to and want this as a project.
- You need full control of the machine: a specific network setup, other software on the same box, data that must stay on hardware you own.
- You run at a scale where a dedicated machine you tune yourself is genuinely cheaper, and you have the person to tune it.
- You are evaluating n8n and want to try it for nothing before committing to anything.
When a managed instance is right
- You want n8n to be a tool you use, not a system you run.
- Nobody on the team wants to be the person who gets the 2 am message.
- You want local billing and support in your language.
- You are a freelancer or agency selling automations to clients and need each client on a clean, isolated instance without running a fleet.
A way to decide
Ask one question: who will own the server next year? If there is a name, and that person is glad to, self-host. If the answer is "me, I suppose" or "we'll figure it out", choose managed; the hours you save are the ones you would have spent not building workflows.
If you are self-hosting today and want out, the move is an export of workflows and credentials, an import into the new instance, a check that each one runs, and a switch of your webhook URLs. Nothing stops in between.