The useful answer
Start with n8n Cloud unless you can explain why you need self-hosting.
Self-hosting may give you more control, but it also gives you Linux, Docker, HTTPS, database, update, backup, monitoring, and recovery jobs. Choose it for a real need, not because a small VPS price looks cheaper.
Four routes
Each route moves work between you and the host.
n8n Cloud
n8n hosting route
- May fit when
- You want n8n to handle the hosting layer and you do not need a self-hosted-only feature.
- Your work
- You build workflows, connect accounts, control users, and decide what data each workflow can reach.
- Check
- Plan limits, execution history, users, data location, available features, and how to export workflows.
Managed n8n hosting from another company
n8n hosting route
- May fit when
- You want a ready-made n8n setup but prefer another host or service package.
- Your work
- The work split changes by provider. Get updates, backups, access, restores, and support promises in writing.
- Check
- Who owns the n8n account, encryption key, domain, database, backups, and move-out process?
Self-managed Docker VPS
n8n hosting route
- May fit when
- You can manage Linux, Docker, HTTPS, a database, backups, updates, logs, and server access.
- Your work
- You own the server and the n8n app. A VPS company normally manages only the hardware and network.
- Check
- Persistent data, a custom encryption key, webhook URL, TLS, updates, and a tested restore.
Larger self-hosted setup
n8n hosting route
- May fit when
- Tests show that one n8n process is not enough or your team needs stricter controls and separate workers.
- Your work
- You may add PostgreSQL, Redis, workers, monitoring, external file storage, and a planned update process.
- Check
- Do not add this setup before measurements show the need and your team can operate every part.
The important data
Workflows are only one part of an n8n backup.
Credentials
n8n stores connections to other services. Protect the encryption key and limit who can view or use each credential.
Database
Workflows, settings, users, and execution records can live in the database. Back it up in a way you can restore.
Files and history
Some workflows handle files or keep execution data. Decide how long to keep it and where large files live.
A copy of the workflow canvas is not a full recovery plan. Test a clean restore with the database, encryption key, required files, environment settings, and the same n8n version.
The public door
Webhooks need a public address, but the editor needs protection.
A webhook is an address another service calls to start a workflow. Your webhook routes may need to be public. That does not mean the n8n editor, database, or server login should be open to everyone. Use HTTPS, a correct public webhook address, and strong access controls.
- 01
Give n8n a stable public address. The domain should keep pointing to the current service after a restart or move.
- 02
Use HTTPS. Protect information while it travels between the caller and your server.
- 03
Protect the editor. Limit users and give each person only the access they need.
- 04
Review risky nodes. Code, file, community, and custom nodes can reach more of the host.
- 05
Keep n8n current. Plan updates and read release notes before changing a production system.
More parts are not automatically better
Scale after a test shows what is full.
n8n documents queue mode for a main process and separate workers. That route also needs Redis and a supported database. More parts can run more work, but they also create more things to update, watch, back up, and recover.
| What a test shows | What to check next |
|---|---|
| One workflow uses too much memory | Fix the workflow, file handling, or execution-data settings before buying a larger system. |
| Too many jobs wait at once | Check concurrency and whether queue mode fits the real workload. |
| Large files fill local disk | Check file retention and whether supported external storage is part of your plan. |
| The editor is slow but workflows are fine | Measure the database, browser, and network separately. |
Quick guide
Choose the simplest route that meets the real need.
| Your situation | Start with | Why |
|---|---|---|
| You want to build workflows, not manage a server | n8n Cloud | n8n handles the hosting layer. |
| You want a ready-made outside service | Managed n8n hosting | It may remove setup work, but read the work split. |
| You need self-hosting and know Linux and Docker | Self-managed Docker VPS | You control the host and accept every server job. |
| Measured load needs separate workers | Larger self-hosted setup | Queue mode can split work across processes. |
Before you pay
Get twelve answers in writing.
Sources and limits
Official n8n guides, not hosting-company promises.
We checked these official n8n pages on August 28, 2026. They support the hosting routes, security checks, and scaling notes. We did not run the same workflows on different hosts or test speed, uptime, support, backups, or recovery times.
- n8n documentation overview — cloud, npm, and self-hosted choices.
- n8n Docker installation — the official container route.
- n8n security overview — security checks for a self-hosted instance.
- n8n security audit — checks for credentials, files, nodes, webhooks, and missing settings.
- n8n queue mode — main process, workers, Redis, and database requirements.
- n8n external storage — plan limits and file-storage behavior.
FAQ
What is the best n8n hosting?
n8n Cloud is the simplest starting route when you do not want server work. A managed third-party service may fit when its work split is clear. A Docker VPS fits only when someone can manage Linux, Docker, HTTPS, updates, backups, and recovery.
Is self-hosting n8n free?
The software route may avoid a cloud subscription, but the server, domain, backups, storage, monitoring, and your time still cost money. Some team, scaling, and external-storage features also depend on the n8n plan.
Does n8n need a VPS?
No. n8n Cloud is hosted by n8n. You can also test n8n locally. Use a VPS when you choose to self-host and need the workflows and webhooks to stay available.
Can normal shared web hosting run n8n?
Do not assume it can. n8n needs an app process that can keep running, saved data, environment settings, and public webhook routes. A normal shared website plan may not allow those things.
When does n8n need queue mode?
Queue mode is for a setup with separate worker processes. Add it when real execution tests show one process is not enough and your team can operate the database, Redis, workers, and shared settings.
Did you test n8n hosting companies?
No. This page compares hosting routes using n8n's official documentation. We did not test speed, uptime, support, busy workflows, or provider backup quality.