For a single workflow running a few hundred executions a day, self hosted n8n cost typically lands between $90 and $150 a month in pure infrastructure: server, storage, backups, a certificate. Add the patching and monitoring hours someone on your team actually has to spend, and the fully loaded number runs $275 to $450 a month. That range assumes a 2 vCPU, 4 GB VPS, daily off-site backups, and two to four hours a month of a person's time billed at a $75 hourly rate. Change any of those assumptions and the number moves, which is the whole point of pricing this out line by line instead of trusting "n8n is open source, so it's free."
Sizing the server to the workload, not the marketing page
n8n's own sizing guidance talks in generalities. The number that actually matters is executions per day, because every execution spins up a workflow run, holds it in memory while nodes fire, and writes the result to the database. Concurrency, not total volume, is what forces you to upgrade the box.
Take a self-service order tracking workflow as the sizing example: a customer texts or emails "where's my order," the workflow looks up the order in the CRM or order system, and replies with status. At 300 lookups a day spread across business hours, that's roughly 25 to 40 an hour at peak, each one a quick API call and a database write. A 2 vCPU, 4 GB VPS from a mainstream provider, listing in the $20 to $40 a month range as of late 2026, handles that load with room to spare.
Push the same workflow to 3,000 lookups a day with several running concurrently during a flash sale, and the memory ceiling becomes the bottleneck before the CPU does. n8n holds execution data in memory until it's written out, so concurrent runs stack up fast. At that volume you're sizing for 8 GB of RAM and a dedicated database instance, not a shared VPS, which moves the server line item closer to $80 to $120 a month. Sizing to today's volume and re-checking quarterly beats guessing once and overpaying for a year.
Storage and backups nobody budgets for
The database grows with every execution you log, and most estimates skip this entirely. At 300 executions a day with full payload logging, average record size around 15 to 20 KB once you include the data being passed between nodes, that's roughly 150 to 180 MB a month of database growth, or about 2 GB a year. Not alarming on its own, but it compounds with every workflow you add, and n8n's default execution retention keeps that data indefinitely unless you set a pruning policy.
Off-site backups are the part people forget to price at all. A nightly snapshot of the database and the n8n data directory, retained 30 days, stored on something like Backblaze B2 or S3 at roughly $6 per terabyte a month, costs very little in raw storage dollars. What it costs is the setup: a cron job or n8n workflow that dumps the database, compresses it, and ships it off-box, tested at least once by actually restoring from it. Budget $5 to $10 a month in storage and an afternoon of setup you won't repeat, but you will maintain.
A reverse proxy and certificates
Let's Encrypt issues free SSL certificates, so the certificate itself costs nothing. The reverse proxy in front of n8n, usually Caddy or Traefik, is also free software. What isn't free is the time to wire it up correctly: pointing DNS at the server, configuring the proxy to request and renew the certificate automatically, and making sure n8n's webhook URLs resolve over HTTPS before any workflow with an incoming webhook actually works.
Caddy's automatic HTTPS handles renewal without a cron job, which is the main reason to pick it over a manually configured Nginx and certbot setup. Even so, initial setup, including firewall rules and a DNS record that propagates cleanly, runs two to four hours the first time. At a $75 hourly rate, that's $150 to $300 as a one-time cost, which amortizes to roughly $15 to $25 a month over the first year. After that it mostly runs itself, with an occasional ten minutes checking that the certificate actually renewed before it expires.
Monitoring and the alert that pages you at 2am
Nobody prices monitoring until after the first outage, and then they overbuy. The minimum viable setup is an uptime check hitting an n8n health endpoint every one to five minutes, plus an alert that reaches a phone, not just an inbox, when it fails. A hosted uptime service in the $10 to $25 a month range covers this.
Log shipping is the piece that turns an outage from "the webhook is failing" into "the webhook is failing because the database connection pool is exhausted." Without it you're SSHing into the box at 2am trying to read raw logs under pressure. Shipping n8n's logs to a lightweight stack, or even just to a log drain with retention, adds setup time but little ongoing dollar cost. The real cost is the 30 to 60 minutes a month of actually reviewing alerts and tuning thresholds so the page that wakes you up at 2am is a page worth waking up for.
Patching: the line item a subscription doesn't have
This is the line item that doesn't exist on a subscription invoice, and it's the one that moves the self hosted n8n cost total the most. n8n ships frequent releases, and 2026's advisory pace means security patches land on a schedule nobody controls. Someone has to track the release notes and security advisories, decide whether a given CVE applies to your deployment, test the upgrade against your actual workflows in a staging instance, and apply it to production without breaking a webhook that a client depends on.
That work runs two to four hours a month in a normal quarter, and spikes higher in a quarter with a critical advisory that demands an out-of-cycle upgrade. At $75 an hour, that's $150 to $300 a month, and it's the item every self-hosted cost comparison that only counts server dollars leaves out entirely. It's also unpredictable by nature: you don't get to choose how many advisories ship in a given quarter, which is exactly why a managed tier prices it into a flat monthly fee instead of asking you to staff it.
The full line-item total, and what it buys you
Add it up for the order tracking example: server at $30, storage and backups at $8, reverse proxy amortized at $20, monitoring tool and review time at $45, patching at $225. That's $328 a month, fully loaded, for one modest workflow on a small instance. Scale the instance up for higher volume and the server and monitoring lines move, but patching stays roughly flat since it's driven by advisory count, not execution count.
What you own at the end of a year of paying that is the server, the workflows, the data, and the configuration, all in your own infrastructure, exportable at any point. Stop paying tomorrow and the workflows still exist on disk. That's the trade a subscription doesn't offer: walk away from n8n Cloud and the workflows stay on n8n's servers, not yours. Whether that ownership is worth $328 a month depends entirely on whether the hours it takes are hours someone already has, or hours you'd have to hire for.
Self hosted n8n cost vs n8n Cloud vs Zapier at the same volume
n8n's own Cloud tiers price by execution volume rather than by server size, starting near $20 to $24 a month for a few thousand executions and stepping up from there as volume and active workflow count grow. At the 300-executions-a-day volume in the order tracking example, roughly 9,000 executions a month, a mid-tier Cloud plan in the $50 to $65 a month range covers it with no server, no patching, and no backup strategy to design.
Compare that to the $328 fully loaded self-hosted number above, and Cloud wins on raw dollars at this volume, every time, unless the hours going into patching and monitoring are hours that were otherwise idle. Zapier prices by task count rather than execution count, with its paid tiers starting under $20 a month for several hundred tasks and scaling into the hundreds of dollars a month at the volumes a multi-step order tracking workflow would actually consume, since Zapier counts each action step as a separate task where n8n counts the whole run as one execution. At low volume, self-hosting rarely beats either hosted option on cost. It starts to win only once execution volume is high enough, and workflow count broad enough, that the hosted tier's per-execution pricing outpaces a flat server bill, which for most teams running a handful of workflows is a volume they haven't reached yet.
When self hosting is the wrong call
The honest answer, most of the time, is don't self-host. If you're running fewer than a few thousand executions a month across one or two workflows, n8n Cloud's lowest tier costs less than a single hour of the patching time self-hosting demands, and it demands that patching time every month, not once. If nobody on the team is willing to own advisory tracking and version upgrades as a recurring responsibility, self-hosting isn't cheaper, it's just unpatched, which is worse than paying for Cloud.
Self-hosting earns its keep when execution volume is genuinely high, when you need the workflow data to live inside your own infrastructure for compliance reasons, or when you're already running other self-hosted tools and the operational muscle exists. Outside those cases, the line-item total in this post is the argument against building it yourself, not for it.
If you're trying to figure out which of these numbers applies to your own volume before deciding anything, our admin cost calculator runs the arithmetic against your actual execution count. And if the honest answer for your team is that the automations matter more than the hosting debate, that is what the Revenue Roadmap and AI automations builds settle, including a self-service order tracking workflow like the one priced out above, inside accounts you already run.
Common questions
Is self-hosted n8n actually free?
The software license costs nothing. The server, storage, certificates, monitoring, and patching time do not, and added together they land around $90 to $150 a month in bare infrastructure, or $275 to $450 once you count the hours someone spends running it.
How much does a self-hosted n8n server cost per month?
A small instance sized for a few hundred daily executions typically runs $20 to $40 a month on a mainstream VPS, before backups, the reverse proxy, monitoring, and patching hours are added.
Is self-hosted n8n cheaper than n8n Cloud?
At low to moderate execution volume, usually no once patching and monitoring hours are counted at a real hourly rate. It starts to win only at execution volumes high enough that Cloud's per-execution pricing outpaces a flat server bill.
How many hours a month does patching self-hosted n8n take?
It varies with how many advisories ship that quarter: typically two to four hours in a quiet one, more after a critical advisory forces an out-of-cycle upgrade. That unpredictability is the real cost, and it's the exact thing a managed Cloud tier prices into its flat monthly fee so you never have to staff it.
