# n8n pricing in 2026: is self-hosting cheaper than Cloud? > n8n Cloud costs €20 to €145 a month for 2,500 to 50,000 executions. Self-hosted n8n is free under its license, so you pay only for a server, about $7 a month. Published 2026-10-02, updated 2026-11-14, by Nick Potts. For agents: [llms.txt](https://ployz.dev/llms.txt) indexes the Ployz docs as Markdown. **TL;DR:** n8n Cloud costs **€20 a month for 2,500 executions**, €50 for 10,000 and about €121 for 50,000, billed annually. Self-hosted n8n is free under its license and has no execution cap, so the bill is the server: a $7.09 Hetzner CX23 handles the first two volumes, and I'd use a $10.59 CX33 at 50,000. That saves about $590 a year at 10,000 executions and about $1,500 at 50,000. - **Pick n8n Cloud if** you don't want to own a server, you're under 2,500 executions, or a small team needs shared projects without paying for Business. - **Self-host if** you're past a few thousand executions a month (one 5-minute schedule already is), your workflows run longer than Cloud's 5- or 40-minute limits, or you want your data on your own server. - **Watch schedules.** A Schedule Trigger every 5 minutes uses about 8,700 executions a month, most of a Pro 10K plan. - **Don't self-host to get around the license.** If your customers build their own workflows on your n8n, you need a commercial agreement either way. - **Run it with Ployz if** you want n8n and Postgres on your server with an https address in a few dashboard steps, or deployed by your coding agent. It's free on any number of servers. n8n is a workflow automation tool, like Zapier or Make, that you can use on n8n's Cloud or host yourself. Its Cloud plans charge per execution, one complete run of a workflow, while the self-hosted Community edition is free with no limit. ## What would your n8n bill be? Move the slider to your monthly production executions. The Cloud rows pick the smallest plan that fits: Starter up to 2,500, Pro 10K up to 10,000, Pro 50K up to 50,000. The server rows stay flat because a self-hosted n8n has no execution quota. *The interactive calculator is on the web page: https://ployz.dev/blog/n8n-pricing* What the calculator leaves out: your time, and n8n's AI credits. Cloud plans include Assistant credits and "AI models without API keys". On a self-hosted instance you bring your own API key for Assistant and pay the model provider directly. ## What does n8n cost at 2,500, 10,000 and 50,000 executions? At 10,000 executions a month, n8n Cloud is **$56.49 a month** on annual billing and a self-hosted server is $7.09. Pay monthly and Cloud costs 20% more. At 50,000 I'd move to a bigger server for headroom, and the gap is still $125.92 a month. | Executions / month | n8n Cloud plan | Cloud, annual (per month) | Cloud, monthly | Own server | Self-hosted total | You save per year (vs annual) | |---|---|---|---|---|---|---| | 2,500 | Starter | €20 = $22.60 | €24 = $27.12 | Hetzner CX23 | $7.09 | $186 | | 10,000 | Pro 10K | €50 = $56.49 | €60 = $67.79 | Hetzner CX23 | $7.09 | $593 | | 50,000 | Pro 50K | €120.83 = $136.51 | €145 = $163.82 | Hetzner CX33 | $10.59 | $1,511 | Server prices are from [Hetzner's cost-optimized cloud page](https://www.hetzner.com/cloud/cost-optimized), after Hetzner's [15 June 2026 price adjustment](https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/). The CX23 (2 vCPU, 4 GB RAM, 40 GB NVMe) is $6.49 plus $0.60 for its IPv4 address, and the CX33 (4 vCPU, 8 GB, 80 GB) is $9.99 plus $0.60. In euros that's €5.99 and €8.99 with IPv4. Both run in Hetzner's EU locations only. Netcup is the other provider I'd look at, and often the better deal. Its VPS 500 (2 vCPU, 4 GB RAM, 64 GB SSD, traffic included) is €8.26 a month incl. VAT on a 12-month term, with datacenters in Europe and Manassas in the US ([netcup VPS plans](https://www.netcup.com/en/server/vps)). Ployz is free on your server, and a custom domain costs nothing extra on it, so with n8n on your own domain through Ployz the 10,000-execution case stays at $7.09 against $56.49. Above 50,000 executions, n8n Cloud has no public price. The self-hosted server doesn't change. What changes is how much CPU your workflows burn, which depends on what they do, not on how many times they run. ## How much does n8n Cloud cost? n8n Cloud has two self-serve plans: Starter at **€24 a month** (€20 billed annually) for 2,500 executions, and Pro at €60 a month (€50 annually) for 10,000. Pro also has a 50,000-execution tier. Above that, n8n Cloud means Enterprise, which is a sales call. Every plan includes unlimited users, workflows and integrations. | Plan | Hosted by | Executions / month | Monthly billing | Annual billing (per month) | |---|---|---|---|---| | [Starter](https://n8n.io/pricing/) | n8n | 2,500 | €24 | €20 | | [Pro (10K)](https://n8n.io/pricing/) | n8n | 10,000 | €60 | €50 | | [Pro (50K)](https://n8n.io/pricing/) | n8n | 50,000 | €145 | €120.83 (€1,450/yr) | | [Business](https://n8n.io/pricing/) | You (self-hosted only) | 40,000 | €800 | €667 | | [Enterprise](https://n8n.io/pricing/) | n8n or you | Custom | Contact sales | Contact sales | | [Community edition](https://docs.n8n.io/deploy/host-n8n/community-edition-features) | You | No limit | Free | Free | The limits that matter besides executions, all from the [pricing page](https://n8n.io/pricing/): | Limit | Starter | Pro | Enterprise | |---|---|---|---| | Concurrent executions | 5 | 20 (10K) / 50 (50K) | 200+ | | Max execution duration | 5 min | 40 min | 40 min | | Saved executions | 2,500 | 25,000 | 50,000 | | Execution log retention | 7 days | 30 days | Unlimited | | Shared projects | 1 | 3 | Unlimited | | Assistant credits / month | 1,600 | up to 9,600 | n/a | | Support | Forum | Forum | Dedicated, with SLA | The 5-minute cap on Starter is the one people hit first. A workflow that pages through a slow API or waits on an LLM can run past it. Business is the odd one out. It's €667 a month and you host it yourself, because n8n says it's [not available on Cloud yet](https://n8n.io/pricing/). You pay for features like SSO, Git version control and multiple environments, not for hosting. ## What counts as an execution in n8n? An execution is one complete run of a workflow, no matter how many steps it has or how much data it moves. A 40-node workflow that runs once is one execution. Only production executions count: runs started by triggers, schedules or polling. Clicking "Execute workflow" in the editor while you build doesn't count ([n8n docs](https://docs.n8n.io/build/understand-workflows/understand-executions)). That's the good part, because Zapier and Make bill per task or operation, so a long workflow costs more every time it runs. The bad part is schedules. n8n's own pricing FAQ says a workflow that runs every 5 minutes uses about 8,600 to 8,900 executions a month ([pricing FAQ](https://n8n.io/pricing/)), because a schedule counts every time it fires, whatever the outcome. Polling triggers like the Google Drive Trigger only count when they find new data, and sub-workflows called from a parent don't count either. | Trigger | Executions a month | |---|---| | Daily schedule | 30 to 31 | | Hourly schedule | about 730 | | Every 5 minutes | about 8,700 | | Webhook | one per incoming request, even an empty one | ## How much does it cost to self-host n8n? Whatever the server costs, because the Community edition is free and has no execution limit. For one person or a small team, that's a **$7.09** Hetzner CX23 running n8n and Postgres side by side. Some guides quote $200 to $800 a month for self-hosting; that's a staffing estimate for a company, not a server bill. The real costs, in the order I'd think about them: 1. **The server.** I'd only go bigger than a CX23 if the workflows do heavy work themselves: big files, long Code nodes, lots of parallel runs. 2. **Your time.** Updates, backups and fixing it when it breaks. With a deploy tool doing the server setup, I'd budget an hour to set it up and a few minutes per update. 3. **AI usage.** You pay OpenAI or Anthropic directly instead of using bundled credits. 4. **A paid license, only if you need it.** Business features (SSO, Git, environments) cost €667 a month and up, self-hosted or not. ## Is n8n free if you host it yourself? Yes, for most people. The self-hosted Community edition is free under n8n's [Sustainable Use License](https://github.com/n8n-io/n8n/blob/master/LICENSE.md), for your own business's internal purposes, personal projects and non-commercial use, with no execution or workflow limits. It's source-available, not open source, so a few commercial uses need a paid agreement. n8n's [license FAQ](https://docs.n8n.io/n8n-community-license/community-license/license-faq) puts it in one line: "If workflows are only created or modified by you or people in your organization, you can use n8n under the Community license for free." It explicitly allows: - Running your business on it, and using it for personal projects, learning or research. - Building automations for clients on your instance, as long as the clients can't create or edit them. - Charging clients for building, setting up and maintaining workflows, and for training and consulting. - Using n8n behind the scenes in your own product, where users trigger automations you built, even with their own connected accounts. - Running several instances. ### What can't you do with the free edition? You can't sell n8n itself. The license FAQ rules out hosting n8n as a service where clients build their own workflows, letting your product's users build or configure workflows (through a custom UI, the API, MCP or an AI agent), forking n8n into your own automation product, white-labeling it, and using license-key features without a paid license. The test is who controls the workflow logic, not whose credentials are involved or whether the user sees n8n's UI. Code in files with `.ee.` in the name is under the separate [n8n Enterprise License](https://github.com/n8n-io/n8n/blob/master/LICENSE_EE.md) and stays locked without a key. According to [n8n's edition comparison](https://docs.n8n.io/deploy/host-n8n/community-edition-features), the Community edition doesn't include: - Projects, and sharing workflows or credentials with other users (only the owner and the creator can access them) - SSO with SAML or LDAP - Environments and Git version control - Custom variables and external secrets - Log streaming (plain logging is included) - External storage for binary data - Multi-main mode (queue mode is included) A free registration with your email unlocks folders, debug in editor and custom execution data. If you're one person, almost none of the locked list matters. If you're a team that needs to share credentials, it matters a lot, and that's where Cloud Pro, with 3 shared projects and admin roles, earns its price. ## What do you lose by self-hosting n8n? Managed upgrades, a few team features, bundled AI and someone else on call. Support isn't on the list, because Cloud Starter and Pro only get forum support too; dedicated support with an SLA is Enterprise-only, hosted or self-hosted. | | n8n Cloud | Self-hosted | |---|---|---| | Upgrades | Pick a release track and update from settings, with a one-to-two-minute restart ([n8n docs](https://docs.n8n.io/deploy/use-n8n-cloud/update-your-version)) | Yours. n8n ships a new minor version most weeks and recommends a full backup before each ([Docker docs](https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker)) | | Sharing | Shared projects on Starter and Pro | Not in the free edition | | AI | Assistant credits and models without your own key | Bring your own API key | | Uptime | n8n's problem | If your server goes down at 3am, webhooks fail until you fix it | | Execution limits | 5 or 40 minutes, 5 to 50 concurrent | None unless you set them, up to your hardware | | Extras | | Custom nodes and bash scripts, which the pricing page marks "available in self-hosted" | ## How do I self-host n8n? You need four things: the official `n8nio/n8n` Docker image, a Postgres database, an https address (webhooks from Stripe, GitHub and most other services won't call plain HTTP), and a volume for `/home/node/.n8n`, where n8n keeps its encryption key. The same pieces work with plain Docker on any server. With Ployz on a Hetzner server it's five steps: **1. Install Ployz on the server.** Point it at a fresh Linux server you can SSH into as root: ```bash ployz up --server root@your-server ``` This installs Ployz on the server and connects it to Ployz Cloud, where the dashboard lives. **2. Add Postgres.** In the dashboard, add the one-click Postgres preset. It's a regular service with a volume, not a managed database. Its password is sealed, so n8n reads it, the host, the user and the database name through references. **3. Add n8n from its image.** Add a service from the Docker image `n8nio/n8n`, listening on port 5678. Give it an https address, then add a volume and mount it at `/home/node/.n8n`. **4. Set the variables.** These names come from n8n's [database](https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/database), [deployment](https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/use-environment-variables/deployment) and [reverse proxy](https://docs.n8n.io/deploy/host-n8n/configure-n8n/basic-configuration/configuration-examples/configure-webhook-urls-with-reverse-proxy) docs. The `${{ postgres.… }}` values are [references](https://ployz.dev/docs/services/variables#reference-another-services-variable) to the Postgres service's variables. Untick **Sealed** for those, since a sealed value can't hold a reference, and the password stays hidden anyway. Seal the encryption key. ```bash DB_TYPE=postgresdb DB_POSTGRESDB_HOST=${{ postgres.PGHOST }} DB_POSTGRESDB_PORT=5432 DB_POSTGRESDB_DATABASE=${{ postgres.PGDATABASE }} DB_POSTGRESDB_USER=${{ postgres.PGUSER }} DB_POSTGRESDB_PASSWORD=${{ postgres.PGPASSWORD }} N8N_ENCRYPTION_KEY= # secret, keep a copy N8N_HOST=n8n.example.com N8N_PROTOCOL=https N8N_WEBHOOK_URL=https://n8n.example.com/ N8N_EDITOR_BASE_URL=https://n8n.example.com/ N8N_PROXY_HOPS=1 GENERIC_TIMEZONE=Europe/Berlin TZ=Europe/Berlin ``` `N8N_WEBHOOK_URL` replaced `WEBHOOK_URL` in n8n 2.35.0. Without it, n8n builds webhook URLs from its internal port 5678 and registers addresses that nothing outside the server can reach. `N8N_PROXY_HOPS=1` tells n8n it sits behind one proxy, which is Caddy on a Ployz server. `GENERIC_TIMEZONE` decides when your Schedule Trigger nodes fire. Use the https address Ployz gives the service, or your own domain, for all four URL variables. **5. Deploy, then open the address** and create the owner account. Add a health check on `/healthz`. Because n8n has a volume, Ployz restarts it on deploy instead of running old and new side by side, so expect a few seconds of downtime per update. The Schedule Trigger runs inside the n8n process, so as long as the service is up, your schedules fire on time. ### How do I back up a self-hosted n8n? A complete n8n backup has two pieces: the Postgres database, and the `.n8n` folder or at least your `N8N_ENCRYPTION_KEY`. Without the key, credentials in a restored database can't be decrypted ([n8n backup docs](https://docs.n8n.io/deploy/host-n8n/keep-n8n-running/backup-and-restore)). 1. **Save the encryption key outside the server**, like in a password manager, on day one. 2. **Keep a copy of the Postgres database off the server.** On Ployz the database gets a restore point on its own server, which covers a bad upgrade but not a dead server. For that, copy a nightly `pg_dump` to object storage or another server, and take a fresh one before every upgrade. 3. **Export workflows and credentials** before every n8n upgrade, from inside the n8n container: ```bash n8n export:workflow --backup --output=/home/node/.n8n/backups/workflows/ n8n export:credentials --backup --output=/home/node/.n8n/backups/credentials/ ``` Writing them under `/home/node/.n8n` keeps them on the volume, so they survive a container restart. Copy the exports off the server with the database dump, so they survive a dead server too. These exports don't include users, execution history or variables, which is why the Postgres backup matters. ## Where Ployz fits I built Ployz so running an app like n8n doesn't mean hand-writing proxy config. n8n gets an https address on your server, so webhooks work from day one. One-click Postgres comes with a restore point. Metrics, searchable logs and crash emails are in the dashboard. Your coding agent can do the setup. Paste one line into Claude Code, Codex or Cursor and it [deploys for you](https://ployz.dev/blog/claude-code-deploy). Every deploy, restart or delete your agent asks for waits for you to approve, including deleting n8n's database volume. Ployz is free on any number of servers. [Deploy to your own server](https://ployz.dev/auth/github). ## FAQ ### Is n8n free for personal use? Yes. The self-hosted Community edition is free for personal projects, learning and your own business's internal workflows, with no execution limit. You pay only for the server. ### What is the cheapest way to run n8n? Self-hosting the Community edition on a small server: about $7 a month on a Hetzner CX23 in Europe, or €8.26 incl. VAT on a Netcup VPS 500 with a US option. n8n Cloud's cheapest plan is €20 a month on annual billing. ### Does n8n Cloud have a free plan? No. Its cheapest Cloud plan is Starter at €24 a month, or €20 on annual billing, for 2,500 executions. The free option is the self-hosted Community edition. ### Do I need a license to use n8n in my SaaS product? Only if your users build or configure workflows. Running automations you built behind the scenes of your product is allowed under the free license, even with your users' own connected accounts. ## How I checked I checked every price on 2026-10-01. n8n prices are in euros on its site. Where I show dollars, I converted at the ECB rate for that day, [1 EUR = 1.1298 USD](https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html). Hetzner prices exclude VAT. License terms come from n8n's license files and FAQ, quoted where I use them. [Self-host n8n on your own server with Ployz](https://ployz.dev/auth/github).