n8n Hosting: Self-Host vs. Cloud — What Actually Makes Sense

The Three Ways to Run n8n

n8n is one of the most capable workflow automation platforms available today — but it's also one of the few that gives you a genuine choice about where and how it runs. Most software forces you onto their infrastructure and charges you accordingly. n8n takes a different approach.

There are three distinct paths. n8n Cloud is their own managed SaaS — sign up, pay monthly, done. Self-hosted on a VPS means n8n runs on your own Linux server on hardware you control. And managed hosting is the hybrid option: someone else sets up and maintains the infrastructure while you focus entirely on building workflows.

Each path is genuinely right for a different kind of operator. The wrong choice doesn't break your business — but it does mean you're either overpaying, under-resourced, or spending time on infrastructure that isn't your competitive advantage. Here's how to think through it.

n8n Cloud: The Zero-DevOps Option

n8n Cloud is the path of least resistance. You create an account at app.n8n.cloud, choose a plan, and have a running n8n instance in under five minutes. Updates happen automatically. SSL is handled. Their team monitors uptime. If something breaks, you submit a ticket.

The advantages are real. You never deal with breaking changes from version updates — n8n Cloud handles the upgrade path, tests it, and rolls it out. You don't need to know what Docker is, what a reverse proxy does, or how to configure environment variables. For non-technical operators or small teams without IT staff, this is a significant benefit.

The limitations are also real. The Starter plan at $20/mo gives you 2,500 executions per month. Pro at $50/mo bumps that to 10,000. If you're running lead enrichment workflows, CRM sync jobs, or any kind of high-volume data processing, you'll hit those limits faster than you expect. You also have less flexibility around custom nodes and environment-level configuration, and your data flows through n8n's own infrastructure — which matters for some industries and not at all for others.

n8n Cloud is the right call for teams that need automation today and have no intention of becoming infrastructure operators. The premium you pay is a premium for someone else's time and expertise — a fair trade if DevOps isn't in your toolbox.

Self-Hosted on a VPS: Full Control

Self-hosting means n8n runs on a Linux server you rent from a cloud provider. A Hetzner CX11 at roughly €4–6/mo or a DigitalOcean Droplet at $6–12/mo will comfortably run n8n for a small business. The server is yours, the data is yours, and there are no execution limits — you can run a million workflows per month at the same cost as running one hundred.

This is where the economics become striking. For high-volume use cases — anything above 3,000–5,000 executions per month — self-hosted is almost always cheaper. Not marginally cheaper. Dramatically cheaper. The cost difference between a $6/mo VPS and a $50/mo n8n Cloud plan compounds quickly over a year.

The tradeoff is operational responsibility. You're on the hook for updates (and testing that the update didn't break your workflows), SSL certificate renewal, database backups, and uptime monitoring. If the server goes offline at 2am, no one is going to fix it for you. The initial setup — Docker Compose, a domain pointed at your IP, a reverse proxy like Caddy — is a one-time investment of a few hours, not ongoing complexity. But it does require someone who's done it before, or the willingness to learn.

Self-hosted on a VPS is the right choice for technical teams, consultants managing infrastructure for clients, and any business with data residency requirements that preclude third-party SaaS.

Railway and Render: The Middle Ground

If the idea of managing a raw Linux server is unappealing but you're comfortable with developer tooling, Railway and Render offer a compelling middle path. Both are PaaS (platform-as-a-service) providers that let you deploy the n8n Docker image without touching a terminal SSH session. You connect a Postgres database, configure environment variables through a web UI, and get SSL handled automatically.

Railway starts at approximately $5/mo for the resources n8n requires and is generally the more reliable choice for production use. Render has a free tier, but it sleeps on inactivity — which is a problem if you're relying on webhook triggers to fire instantly. A sleeping instance misses the webhook.

The tradeoff versus a raw VPS: slightly less granular control, and you're still subject to the pricing model of the PaaS provider as your usage scales. The tradeoff versus n8n Cloud: you manage your own updates and configuration, but execution limits disappear. It's a reasonable position for developers who build and ship things but aren't sysadmins by training.

Cost Breakdown

The math is straightforward. If your workflows run frequently — monitoring jobs, scheduled syncs, multi-step automations triggered by events — execution counts accumulate fast. Five workflows running every 15 minutes generates over 14,000 executions per month. On n8n Cloud Pro, you've already exceeded the plan limit. On a self-hosted instance, nothing changes.

When Each Option Makes Sense

• N8N CLOUD Non-technical operator who needs automation working today. Low-to-medium execution volume. No IT staff. Willing to pay a premium to never think about infrastructure.
• SELF-HOSTED VPS Technical team or consultant-managed instance. High execution volume. Cost-sensitive. Data residency requirements or preference for full control over configuration and custom nodes.
• RAILWAY / RENDER Developer-comfortable but not a Linux sysadmin. Medium execution volume. Wants straightforward deploys without managing raw server infrastructure.
• MANAGED Business owner who wants the economics of self-hosting — unlimited executions, data on your own server — without learning Docker, SSL certificates, or server administration.

The Managed Option

There's a fourth path that doesn't fit neatly into the technical categories above: paying a consultant to handle the infrastructure side completely. You get the full economics of self-hosting — unlimited executions, your data on your server, no monthly SaaS premium at scale — without needing to understand what any of that means to actually configure it.

Setup covers the server provisioning, Docker installation and configuration, n8n installation, domain configuration, SSL certificates, database setup, automated backups, and uptime monitoring. You get a URL and the credentials to log in. Everything else was already handled.

This is the option that makes sense for business operators whose time is worth more than the learning curve, and who want the right infrastructure without becoming infrastructure operators. It's what we offer — setup, configuration, ongoing maintenance, and updates. You focus on building workflows that move your business forward.

The honest version of this decision is simple: pick n8n Cloud if you want zero operational involvement and have modest execution needs. Pick self-hosted if you have the technical capacity or want to hire someone who does. The worst outcome is landing on n8n Cloud at $50/mo with 20,000 executions per month when a $6/mo server and a few hours of setup would have handled it indefinitely.