In this guide
- What changes when you self-host n8n
- Choose by workload, not by the n8n logo
- Personal or learning automations
- Public webhooks and client-facing workflows
- Automation that processes files or runs frequently
- Five VPS checks before you pay
- A simple decision path
- Compare the operating checklist before choosing a deal
Short answer: the right VPS for n8n is the one that matches your workflow volume and leaves you with a workable backup and upgrade path. A cheap plan can be enough for a personal automation; it is not automatically a good production host for public webhooks, long-running jobs, or workflows that retain lots of execution data.
What changes when you self-host n8n
n8n can run in the cloud or on infrastructure you manage. Self-hosting gives you more control over where the service and its credentials live, but it also makes you responsible for HTTPS, updates, backups, monitoring, and recovery. The official n8n hosting documentation covers Docker, server setups, configuration, and updating; read it before selecting a provider.
That distinction matters when comparing VPS offers. The question is not simply “which VPS has the most RAM for the price?” It is whether the plan gives you enough room to operate the workflows you actually have and to recover when an update, credential, or webhook goes wrong.
Choose by workload, not by the n8n logo
Personal or learning automations
A small instance can be reasonable when a single person runs a handful of low-frequency workflows and can tolerate maintenance windows. Prioritize a provider that makes it practical to back up data and upgrade later. Buying a long prepaid term before you know the execution pattern is usually unnecessary.
Public webhooks and client-facing workflows
Once third-party services call your instance, uptime and HTTPS become part of the product. Check how you will expose the service behind a reverse proxy, set the public webhook URL, renew certificates, and respond to a failed deployment. A discount is not a substitute for a recovery plan.
Automation that processes files or runs frequently
Execution history, logs, and binary data can turn disk capacity into the first constraint. Measure the size and frequency of real jobs after launch. If workflows download files, transform media, or retain long histories, plan storage and cleanup before increasing CPU just because it is advertised.
Five VPS checks before you pay
- Memory headroom: leave room for the operating system, container runtime, n8n, and any database or reverse proxy you run on the same machine. A plan that only works when nothing else happens is not stable capacity.
- Storage and backup: decide where workflow data, credentials, logs, and any binary data will live. Confirm how you will take a backup and test a restore, not merely whether the provider displays the word “backup”.
- Network and region: select a region based on your users and the APIs your workflows call. Region names alone do not guarantee latency or routing quality.
- Public exposure: if webhooks are public, plan HTTPS, access control, updates, and incident response. n8n documents reverse-proxy webhook configuration; do not leave a test installation exposed as a production service.
- Upgrade and exit: read the renewal terms, snapshot policy, migration options, and refund conditions. An annual promotional plan should still let you move if the service outgrows it.
A simple decision path
Start with a short list of actual requirements: number of active workflows, whether webhooks are public, whether files are processed, where users are, and who will handle updates. Then compare providers on the total cost for the period you intend to use, including IPv4, backup, snapshots, and renewal—not only the headline monthly equivalent.
Use the VPS Price Finder to narrow the budget, region, and memory range, then validate the final plan on the provider’s official page. If you are deciding between a cloud sandbox and a server you operate, see AI Agent: cloud sandbox or VPS? for the operational trade-off.
Editorial note, checked October 23, 2026: this guide does not promise a specific minimum specification or provider price. n8n workload, deployment design, and provider terms vary; verify the current documentation and checkout conditions before purchase.
Compare the operating checklist before choosing a deal
For a cross-application checklist covering n8n, Coolify, backups, upgrade paths and the full cost of a self-hosted VPS, see VPS for self-hosted apps: n8n, Coolify and a practical buying checklist.
Get deal alerts, price checks, and reader questions in one place.