n8n Cloud vs. Self-Hosted: Which Is Right for You?

You need workflow automation. You've chosen n8n. Now comes the deployment decision that will determine your total cost of ownership, data security posture, and operational overhead for the next 2-3 years.

This guide cuts through the marketing speak. You'll get real numbers, specific technical requirements, and a decision framework based on what actually matters to professional services firms.

Start here. Everything else is secondary to understanding what you'll actually pay.

n8n Cloud Pricing (as of 2024)

• Starter: $20/month (5,000 executions)
• Pro: $50/month (10,000 executions)
• Enterprise: Custom pricing (starts around $500/month for 100,000+ executions)

Self-Hosted Total Cost of Ownership (Annual)

• DigitalOcean Droplet (4GB RAM, 2 vCPUs): $288/year
• AWS t3.medium (4GB RAM, 2 vCPUs): $360-420/year depending on region
• Database backup storage (S3 or equivalent): $24-60/year
• SSL certificate (Let's Encrypt): $0
• DevOps time for initial setup: 8-12 hours
• Monthly maintenance: 2-3 hours

Break-even analysis: If you're running more than 10,000 executions monthly and have someone on staff who can handle basic Linux administration, self-hosting pays for itself within 6 months.

Choose Cloud if you match two or more of these criteria:

You have no dedicated IT staff. Your "tech person" is a paralegal who also manages your case management system. You need something that works tomorrow, not in two weeks after troubleshooting Docker networking issues.

Your workflows are client-facing. You're building intake forms, client portals, or automated status updates. You need 99.9% uptime guarantees and can't afford to be the person getting paged at 2am when the server goes down.

You're running compliance-light operations. Your data doesn't include HIPAA-protected health information, classified government documents, or financial records subject to SOC 2 requirements. Standard cloud security is sufficient.

You value speed over cost. You'd rather pay $600/year and have automation running this week than save $300/year but spend 12 hours on setup and configuration.

What You Actually Get with Cloud

Automatic updates. New nodes, security patches, and feature releases deploy without your involvement. No maintenance windows, no version compatibility testing.

Built-in monitoring. Execution logs, error tracking, and performance metrics in the dashboard. No need to configure Prometheus, Grafana, or log aggregation.

Instant scaling. Your workflow suddenly needs to process 50,000 records instead of 5,000? Cloud handles it. Self-hosted requires you to resize your instance and potentially deal with downtime.

Support SLA. Enterprise plans include guaranteed response times. When your billable hour tracking automation breaks, you get help within 4 hours, not "whenever you figure it out."

Cloud Limitations You Need to Know

Data residency is non-negotiable. n8n Cloud runs on AWS in specific regions. If your client contracts require data to stay in Canada or the EU, verify n8n's current hosting regions before committing.

No custom node installation. You're limited to n8n's official node library plus community nodes that pass their security review. If you need a proprietary integration with your practice management system, you're stuck.

Execution timeout limits. Cloud plans enforce maximum execution times (typically 5-10 minutes). Long-running data migrations or complex document processing may hit these limits.

Export limitations. While you can export workflows, you cannot easily migrate your execution history, credentials, or environment variables to a self-hosted instance if you decide to switch later.

Choose self-hosting if you match two or more of these criteria:

You handle regulated data. Client trust accounts, medical records, tax returns, or any data subject to specific storage and access requirements. You need to prove exactly where data lives and who can access it.

You have existing infrastructure. You already run on-premises servers or maintain a private cloud. Adding n8n to existing infrastructure costs you almost nothing.

You need custom integrations. Your firm uses proprietary software, legacy systems, or internal tools that require custom-built nodes. Self-hosting lets you install anything.

You're processing high volumes. Running 100,000+ executions monthly? Self-hosting costs $30-40/month versus $500+ for Cloud Enterprise.

Technical Requirements (Minimum Specs)

Server specifications:

• 4GB RAM (8GB recommended for production)
• 2 CPU cores (4 cores for heavy workflows)
• 20GB storage (SSD preferred)
• Ubuntu 22.04 LTS or Debian 11

Required skills on your team:

• Basic Linux command line (apt, systemctl, nano/vim)
• Docker and Docker Compose fundamentals
• Nginx or Caddy reverse proxy configuration
• PostgreSQL or MySQL basic administration

Time investment:

• Initial setup: 8-12 hours (includes SSL, backups, monitoring)
• Monthly maintenance: 2-3 hours (updates, log review, backup verification)
• Quarterly security reviews: 4-6 hours

Self-Hosting Setup Reality Check

You will need to handle:

SSL certificate management. Let's Encrypt certificates expire every 90 days. Set up auto-renewal or you'll wake up to broken workflows when certificates expire.

Database backups. Configure automated daily backups to S3 or equivalent. Test restoration quarterly. One corrupted database without backups means rebuilding every workflow from scratch.

Security updates. Subscribe to n8n's GitHub releases and security advisories. Apply patches within 48 hours of critical vulnerabilities being announced.

Monitoring and alerting. Set up UptimeRobot or similar to ping your instance every 5 minutes. Configure alerts to Slack or email when n8n goes down.

Credential encryption. n8n encrypts stored credentials, but you manage the encryption key. Lose the key, lose access to all your API credentials and OAuth tokens.

Choose n8n Cloud if:

• Annual execution volume under 120,000
• No regulatory requirements for data location
• No dedicated IT staff or DevOps experience
• Need to be operational within 24 hours
• Client-facing workflows requiring high uptime

Choose Self-Hosted if:

• Annual execution volume over 120,000
• Data must stay in specific geographic regions
• Subject to HIPAA, SOC 2, or similar compliance frameworks
• Need custom nodes or proprietary integrations
• Have existing server infrastructure and Linux expertise

Moving from Cloud to Self-Hosted: Export all workflows as JSON files before canceling your Cloud subscription. Credentials and execution history do not transfer. Budget 4-6 hours to recreate credentials and test all workflows in your self-hosted environment.

Moving from Self-Hosted to Cloud: Import workflow JSON files through the Cloud interface. Reconfigure all credentials (API

keys, OAuth connections). Verify webhook URLs have updated to Cloud endpoints. Budget 3-4 hours for migration and testing.

For firms under 10 people with standard automation needs (document generation, email workflows, CRM

updates), n8n Cloud is the correct choice. You'll pay $240-600 annually and avoid operational headaches.

For firms with dedicated IT resources, high execution volumes, or regulatory requirements around data storage, self-hosting delivers better economics and necessary control. Expect to invest 12 hours upfront and 3 hours monthly, but you'll save $200-400 annually while maintaining complete data sovereignty.

The wrong choice costs you either money (overpaying for Cloud when you could self-host) or time (troubleshooting self-hosted issues when you should be billing clients). Match your decision to your actual technical capacity and regulatory requirements, not aspirational DevOps skills your team doesn't have.