n8n Cloud listed Starter at EUR 20, Pro at EUR 50 and Business at EUR 667 a month on annual billing in November 2026. The self-hosted Community edition has no license fee, so the cost is the server plus the person who upgrades, backs up and watches it.
Leave with: an operating-responsibility and recovery sheet.
Download the editable worksheet (CSV) →Bring: workflow workload, required features and runtime owner.
n8n runs in two ways: on n8n's Cloud, or on your own server. The self-hosted Community edition needs no license key. Paid editions add features on top, whichever way you host.

What it costs
On Nov 10, 2026, n8n's pricing page showed Cloud plans billed annually at:
| Plan | Per month, billed annually |
|---|---|
| Starter | EUR 20 |
| Pro | EUR 50 |
| Business | EUR 667 |
Those prices were shown in euros. Monthly billing was not on the page we captured. See the n8n pricing record for the dated capture.
Self-hosted Community has no software charge. You pay for a server, a database and storage, and for the hours someone spends on upgrades, backups and fixing it at the wrong moment. A small server can be cheap: the one we budgeted for our own scheduled jobs was $6 a month including Postgres.
What Cloud takes off your plate
n8n runs the instance, applies upgrades and keeps it reachable for incoming webhooks. Your team still owns the workflows: credentials, field mappings, retries and what each write does to the CRM.
n8n bills Cloud by workflow executions. One execution covers a whole workflow run, which counts differently from Zapier tasks or Make operations. Count your workflows and how often each runs before picking a plan. The n8n vs Zapier and n8n vs Make comparisons cover the unit differences.
What self-hosting adds
Someone has to own the runtime, the database, upgrades, backups, access, TLS and monitoring. Incoming webhooks need the instance to be up when they arrive, or the sender has to retry.
We didn't run n8n for our GTM jobs. We ran our own scripts on a schedule, and they failed the way self-hosted jobs fail:
- A reply watcher ran on a laptop cron, worked for five days, then stopped. macOS had blocked cron from reading the project folder. It logged 2,422 lines of the same error and nobody saw them.
- A weekly job poller stopped for the same reason and never completed its cycle.
- An API started returning HTTP 402. The code caught the error and returned an empty list, so the job reported "no results" for 103 of 105 inputs.
None of those were code bugs in the workflow logic. They were hosting and monitoring gaps, which is the work self-hosting hands you. We moved our jobs to a small server with GitHub Actions as a fallback.
Pick by who will own it
| Situation | Choose |
|---|---|
| Nobody on the team will patch and monitor a server | Cloud |
| Webhooks must be received at any hour | Cloud, or self-hosted with uptime monitoring |
| Data must stay on your infrastructure | Self-hosted |
| You need SSO, environments or Git sync | Check which paid edition includes it, for either hosting |
| You run workflows for clients | Read n8n's license terms for that use |
Before relying on either
- Build one real workflow and break it on purpose: an expired credential, a timeout, a duplicate event.
- Check that a failure produces an alert someone reads.
- Add a freshness check: the last time each job wrote output.
- If self-hosting, restore a backup to a fresh instance and run a workflow on it.
- Have someone other than the builder change a field mapping and deploy it.
See n8n alternatives and workflow automation tools for the other options.
Questions buyers ask
How much does n8n Cloud cost?
On Nov 10, 2026 the pricing page showed Starter EUR 20, Pro EUR 50 and Business EUR 667 per month, billed annually.
Is self-hosted n8n free?
The Community edition has no license fee. You pay for the server, database and storage, and for someone to upgrade, back up and monitor it.
Should I self-host n8n?
Only if someone will own uptime, upgrades, backups and alerts. Our own self-run scheduled jobs failed without an alert twice from a permissions change and once from a swallowed HTTP 402.