Self-hosting n8n can have the lowest cash cost, but managed hosting often has the lower total cost for teams without spare DevOps capacity. The honest comparison includes the server, storage, backups, monitoring, updates, security work, recovery testing, and the value of the person responsible for keeping workflows online.
Why the VPS price is not the full cost
A small VPS may look inexpensive. That invoice buys compute; it does not automatically provide a production service. Someone still needs to install n8n, configure persistent data, expose HTTPS, set the public webhook URL, protect credentials, monitor disk and memory, apply updates, and recover the system when something fails.
The cost gap between self-hosted and managed n8n therefore depends less on the server price than on operational maturity.
Self-hosted n8n cost categories
1. Compute and storage
Your workload determines the server size. Short API synchronizations may run comfortably on modest resources, while AI, file-processing, browser, and high-concurrency workflows can use substantially more memory and CPU. Storage grows with execution history, binary data, logs, and backups.
Do not size only for idle memory. Measure peak execution behavior and leave headroom for upgrades, database maintenance, and failed workflows that retry.
2. Database and persistence
A simple instance can use SQLite with a persistent n8n data directory. Larger or horizontally scaled setups commonly use PostgreSQL. An external database adds another service to secure, back up, monitor, and restore.
The critical question is not “Do we have a backup?” but “Can we restore the complete instance within an acceptable time?” Workflows alone are not the whole system; credentials, configuration, encryption keys, binary data, and webhooks also matter.
3. Domain, HTTPS, and networking
Production webhooks need a stable public URL. Self-hosters normally configure DNS, a reverse proxy such as Caddy or Nginx, TLS certificates, forwarded headers, firewall rules, and the correct n8n host, editor, and webhook environment variables.
A configuration that opens the editor is not automatically safe. Administrative access, webhook endpoints, and internal services have different exposure requirements.
4. Updates and compatibility testing
n8n evolves quickly. Updates can contain security improvements, node changes, migration work, and behavior changes. A responsible update process includes a backup, release-note review, version pinning strategy, staging or representative tests, deployment, and a rollback path.
Using a floating latest image without testing makes the update process easy to trigger and hard to trust.
5. Monitoring and incident response
At minimum, monitor process health, HTTP reachability, disk capacity, memory pressure, container restarts, database availability, backup success, and failed executions. Then decide who receives alerts and who can act on them.
A workflow that fails silently for three days may cost more than months of hosting.
6. Security
Security work includes operating-system updates, firewall policy, SSH access, credential handling, encryption-key protection, authentication, log exposure, community-node review, and webhook design. n8n also provides a security audit that can report credential, database, filesystem, node, and instance risks.
An illustrative monthly cost model
Use this model with your own numbers:
Infrastructure: server + storage + database + backup storage + monitoring.
Routine operations: monthly hours for updates, backup review, capacity checks, and support.
Incident allowance: expected hours for failures, multiplied by the fully loaded hourly cost of the responder.
Downtime impact: lost leads, delayed orders, missed alerts, or manual catch-up work.
For example, if a low-cost server requires two hours of skilled attention each month, the labor can easily exceed the infrastructure bill. If your team already operates a container platform and the extra instance adds almost no work, self-hosting becomes much more attractive.
Managed hosting cost categories
Managed hosting moves many operational costs into a subscription. The provider may include deployment, HTTPS, monitoring, backups, updates, and support, but the boundary varies. You still own workflow logic, credentials for third-party services, API usage charges, data-quality decisions, and business outcomes.
Some providers charge by workflow executions. Others charge by fixed workspace resources or underlying cloud consumption. Compare the billing unit with your workload rather than assuming one model is always cheaper.
When self-hosting is the better choice
You already run reliable container, database, backup, and monitoring infrastructure.
You have clear security ownership and an on-call path.
You need infrastructure-level customization or a specific data location.
You can test updates and restores without improvising in production.
Your workload economics strongly favor owned capacity.
When managed n8n hosting is the better choice
You want to build automations, not operate servers.
No one on the team is clearly responsible for Docker, TLS, backups, and incidents.
A missed webhook or failed workflow has real business impact.
You need a faster launch and a known support path.
You value curated starting workflows in addition to infrastructure.
A simple break-even calculation
Calculate:
Self-hosted total = infrastructure + operations hours + expected incident cost + downtime impact.
Managed total = subscription + third-party API costs + remaining workflow administration.
If the managed premium is smaller than the monthly value of the operational time it removes, managed hosting is economically rational—even when the VPS invoice is lower.
Frequently asked questions
Is self-hosted n8n free?
The standard self-hosted Community Edition can be used without a Cloud subscription, subject to n8n’s license terms. Infrastructure, storage, backups, maintenance, and labor are not free.
Do I need Docker to self-host n8n?
No, n8n can also be installed with npm, but Docker is the most commonly documented production path. Beginners who do not want to manage either can use n8n Cloud or a managed host.
Does managed hosting include third-party API charges?
Usually not. OpenAI, Google, Shopify, messaging, video, email, and other external services keep their own pricing and usage limits.
Bottom line: self-hosting wins when infrastructure operations are already a core competency. Managed hosting wins when reliability and saved time matter more than minimizing the server invoice. If you prefer the latter and want curated workflow installation as part of onboarding, review N8nPort alongside the official n8n Cloud plans.