n8n Cloud Pricing in 2026: What You’ll Actually Pay (and When to Self-Host Instead)

Disclosure: This post contains one or more links to providers we have a real, registered affiliate/referral relationship with. We may earn a commission at no extra cost to you if you sign up through them.

If you’ve started building workflow automations and landed on n8n, you’ve probably hit the same wall everyone does: the pricing page tells you a starting number, but not what you’ll actually pay once your workflows scale. Execution-based pricing sounds simple until you have a dozen workflows firing on webhooks, cron schedules, and API polling loops all at once.

This guide breaks down n8n cloud pricing tier by tier, flags the costs that catch people off guard, and walks through the math on self-hosting n8n on your own infrastructure instead — including a working Docker Compose setup you can deploy today.

What n8n Actually Is (Quick Context)

n8n is an open-source workflow automation tool — think Zapier or Make, but self-hostable and node-based, with the ability to write custom JavaScript directly inside workflow steps. It connects APIs, databases, webhooks, and internal services without requiring you to write a full integration layer from scratch.

Because the core project is fair-code licensed and available as a Docker image, you have two real paths to running it:

n8n Cloud — a managed SaaS offering, billed monthly, scaled by workflow executions.

Self-hosted n8n — you run the container yourself on a VPS, paying only for the server.

Both are legitimate choices depending on your team size, technical comfort, and how many executions you’re actually running per month.

n8n Cloud Plan Breakdown

n8n Cloud pricing is structured around three main variables: number of active workflows, execution volume, and feature access (things like environments, SSO, and advanced permissions). The tiers roughly break down like this:

Starter — entry-level tier aimed at solo builders and small teams. Includes a capped monthly execution allowance (commonly a few thousand executions/month), a limited number of active workflows, and community support only.

Pro — the tier most small businesses land on. Higher execution caps, more active workflows, shared team workspaces, and priority support.

Enterprise — custom pricing, negotiated directly with n8n’s sales team. Includes SSO/SAML, audit logs, dedicated infrastructure options, and SLA-backed uptime guarantees.

Exact dollar figures shift periodically as n8n adjusts its packaging, so always check the official n8n pricing page before budgeting — don’t rely on screenshots or third-party recaps, including this one, for the current number.

What matters more than the sticker price is understanding what counts as an execution, because that’s where budgets quietly blow up.

Hidden Costs to Watch For

The advertised monthly price is rarely the full story. Here’s what actually drives your bill up over time:

Execution counting — every workflow run counts as an execution, even failed ones and ones triggered by a single webhook ping. A workflow that polls an API every minute burns through your allowance fast — that’s 1,440 executions/day from one workflow alone.

Overage charges — once you exceed your plan’s execution cap, you’re either rate-limited, forced to upgrade, or charged per-execution overage fees depending on the plan.

Active workflow limits — cloud plans often cap how many workflows can be active (not just built) at once. Testing and staging workflows can eat into that limit if you’re not archiving unused ones.

Data retention — execution history and logs beyond a certain window may require a higher tier to retain, which matters if you need to debug something that happened two weeks ago.

Add-on seats — team collaboration features are often priced per additional user once you go beyond the base seat count.

If your automations are lightweight — a few daily Slack notifications, a handful of CRM syncs — cloud pricing is genuinely reasonable. If you’re running high-frequency polling workflows or processing large data batches, the execution model starts working against you.

Self-Hosting n8n: The Cost Comparison

Because n8n ships as an open-source Docker image, you can run the exact same automation engine on your own server for the price of the VPS — no execution caps, no per-seat charges, no overage billing. The tradeoff is that you’re responsible for uptime, backups, and updates.

Here’s a minimal but production-usable docker-compose.yml to get n8n running with persistent data and a Postgres backend:

version: "3.8"

services:
  postgres:
    image: postgres:16
    restart: unless-stopped
    environment:
      POSTGRES_USER: n8n
      POSTGRES_PASSWORD: change_this_password
      POSTGRES_DB: n8n
    volumes:
      - postgres_data:/var/lib/postgresql/data

  n8n:
    image: n8nio/n8n:latest
    restart: unless-stopped
    ports:
      - "5678:5678"
    environment:
      DB_TYPE: postgresdb
      DB_POSTGRESDB_HOST: postgres
      DB_POSTGRESDB_DATABASE: n8n
      DB_POSTGRESDB_USER: n8n
      DB_POSTGRESDB_PASSWORD: change_this_password
      N8N_HOST: automation.yourdomain.com
      N8N_PROTOCOL: https
      WEBHOOK_URL: https://automation.yourdomain.com/
      GENERIC_TIMEZONE: UTC
    volumes:
      - n8n_data:/home/node/.n8n
    depends_on:
      - postgres

volumes:
  postgres_data:
  n8n_data:

Bring it up with:

docker compose up -d

Then put it behind a reverse proxy (Caddy or Nginx) for TLS termination, and you have a fully functional, unlimited-execution n8n instance. We cover the full reverse-proxy and TLS setup in our Docker Compose deployment guide if you want the complete walkthrough.

Real Numbers: Cloud vs. Self-Hosted

To put this in perspective, a small 2GB/2vCPU VPS from a provider like DigitalOcean or Hetzner typically costs between $6 and $12/month — and can comfortably run n8n plus Postgres for low-to-moderate workflow volume. Compare that to a cloud Pro-tier plan, and the break-even point usually arrives faster than people expect, especially once you factor in execution overages.

The catch is that self-hosting shifts responsibility onto you:

You manage OS updates, Docker image updates, and security patching.

You need your own backup strategy for the Postgres volume.

You need uptime monitoring, since there’s no vendor SLA watching your instance for you.

You handle scaling manually if execution volume grows.

That last point is where a lot of self-hosted n8n setups quietly fail — nobody notices the container crashed until a client complains their automation didn’t fire. Setting up external uptime monitoring through something like BetterStack closes that gap cheaply, pinging your webhook endpoint or n8n health check on a schedule and alerting you the moment it goes down.

When Cloud Makes More Sense Than Self-Hosting

Self-hosting isn’t automatically the right call. Cloud is usually the better option when:

You don’t have DevOps bandwidth to manage patching and backups.

You need enterprise features like SSO/SAML out of the box.

Your execution volume is genuinely low and predictable.

You want a support contract and SLA rather than being your own on-call engineer.

Self-hosting wins when execution volume is high, you already run infrastructure for other services, or you want full control over data residency and retention — which matters a lot if you’re processing anything sensitive through your workflows.

If you’re already running other self-hosted tools on a VPS, adding n8n to the same box (or a small dedicated one) is usually the most cost-efficient path. We go deeper into stacking multiple self-hosted services efficiently in our guide to self-hosting your DevOps toolchain.

Migrating Between Cloud and Self-Hosted

One underrated advantage of n8n’s architecture is that migration isn’t a one-way door. Workflows are portable JSON exports, so you can:

1. Build and prototype on n8n Cloud while your automation needs are small.
2. Export workflows once execution volume or costs justify moving.
3. Import them into a self-hosted instance without rebuilding from scratch.

This makes it low-risk to start on cloud and migrate later once you understand your actual execution patterns — which is honestly the smartest way to approach the pricing decision rather than guessing upfront.

Choosing a VPS for Self-Hosted n8n

If you decide to self-host, the VPS choice matters more than people assume. You want:

At least 2GB RAM (n8n plus Postgres is lightweight but not trivial under load)

SSD-backed storage for database performance

A provider with snapshot/backup support baked in

Reasonable network latency to the APIs your workflows call most often

DigitalOcean and Hetzner both offer droplets/servers in this range at low monthly cost, with straightforward Docker support and one-click backups. If you want managed database hosting instead of running Postgres in the same container stack, that’s a worthwhile upgrade once your automation becomes business-critical.

Recommended: Want to explore DigitalOcean yourself? DigitalOcean is a direct vendor link (not an affiliate/tracked link).

FAQ

Does n8n Cloud have a free plan?
n8n typically offers a free trial period rather than a permanent free tier for cloud hosting. For a genuinely free option long-term, self-hosting the open-source Docker image on your own server is the way to go — you only pay for the VPS.

What counts as an “execution” in n8n pricing?
Each time a workflow runs from start to finish counts as one execution, regardless of whether it succeeds, fails, or is triggered manually, by webhook, or by schedule. A single workflow polling an API every few minutes can consume thousands of executions per month on its own.

Is self-hosted n8n really free?
The software itself is free under n8n’s fair-code license, but you still pay for the server it runs on, plus your own time for maintenance, updates, and monitoring. “Free” software isn’t the same as “zero-cost” infrastructure.

Can I switch from n8n Cloud to self-hosted later?
Yes. Workflows export as JSON and import cleanly into a self-hosted instance, so you can start on cloud and migrate once your execution volume justifies running your own server.

How many executions does a typical small business need per month?
It varies enormously, but a business running a handful of automations — form submissions, CRM syncs, notification workflows — often stays in the low thousands of executions per month, which usually fits comfortably within entry-level cloud tiers.

Is n8n cloud pricing worth it compared to Zapier or Make?
n8n generally offers more generous execution limits per dollar than Zapier, and more flexibility for custom logic than Make, but the comparison depends heavily on your specific workflow complexity — it’s worth testing all three against your actual use case before committing.

Final Take

n8n cloud pricing works well for teams that want a managed, zero-maintenance automation platform and have moderate, predictable execution volume. Once your workflows scale into high-frequency polling or large data batches, the execution-based model starts costing more than a self-hosted VPS running the same open-source image. Start with cloud if you’re prototyping, track your execution counts honestly, and migrate to self-hosting once the math tips in that direction — the workflow export format makes that switch far less painful than most SaaS-to-self-hosted migrations.