Last updated September 2026
For teams where automation data genuinely can't leave your own infrastructure -- proper server sizing, security configuration, and a real handoff, not just "here's a Docker container."
Quick answer: Self-hosted n8n runs entirely on infrastructure you control -- typically a small VPS costing $5-$20/month for light-to-moderate volume, with no per-execution cost at all. It's the right call when data residency or compliance requirements mean automation data can't touch third-party servers, not just a way to save money.
We'd rather tell you honestly than push infrastructure you don't need yet.
Most small-to-mid volume setups run comfortably on a $5-$20/month VPS. Higher-volume or production workloads with redundancy needs cost more, but even then it's typically a fraction of what task-based or operation-based billing would charge at the same volume. The tradeoff isn't really about money at low volume -- it's about who owns the infrastructure.
Every setup starts with the same process we use for everything — audit first, then build what the audit actually finds, not the other way around.
A small VPS ($5-$20/month) handles light-to-moderate volume comfortably. Higher-volume or production workloads with redundancy needs require more resources -- sized precisely based on your actual execution volume during the audit, not guessed upfront.
Self-hosting keeps your automation data on infrastructure you control, which is often a real requirement for data residency or compliance frameworks. It's a necessary piece, not automatically sufficient on its own -- proper security configuration, access controls, and backups still matter.
You are, ultimately -- self-hosting means the server, its security patches, and access controls are your responsibility (or whoever you designate). We configure it properly at setup and can hand off documentation, or continue managing it as an ongoing arrangement.
Yes -- workflows built on n8n Cloud can be exported and imported into a self-hosted instance. It's a common path: start on Cloud to validate the approach, move to self-hosted once volume or compliance needs justify the switch.
That's exactly what a Discovery Call is for — an honest look at your actual compliance needs and volume before we recommend anything.
Tell us about your business →