← THE OBSERVATORY

A year of self-hosted n8n: what it costs, what it saves

Every automation we run, the server bill it sits on and the per-task SaaS pricing it replaced, with the workflow counts to show for it.

09 JUN 2026 · 9 MIN READ · BY THE SYSTEMS PRACTICE

Twelve months ago we moved every internal automation off per-task SaaS platforms and onto a self-hosted n8n instance, then kept the meter running. This is the honest accounting: the server bill, the workflows it carries, and the pricing model it replaced.

What the bill actually is

The whole estate runs on one modest virtual server with a fixed monthly cost, backed up nightly. That figure has not moved all year. The workflow count has: what started as a handful of migrated automations is now the connective tissue of the operation, from lead routing and invoice chasing to report generation and the alerts that wake the right person.

1 billONE FIXED SERVER COST CARRIES EVERY WORKFLOW. THE COUNT GROWS, THE BILL DOES NOT

Where the saving actually comes from

Per-task pricing has a property that only becomes visible at scale: it charges you for succeeding. Build an automation that fires ten thousand times a month and the platform congratulates you with a bigger invoice. The busier our workflows became, the wider the gap grew between the fixed server cost and what the same volume would have billed on per-task plans.

The second saving is quieter. Owning the instance means no plan limits shaping the architecture. Workflows are as chatty, as frequent and as numerous as the job requires, because the marginal cost of one more execution is zero.

A platform that charges per task is charging you a success tax on the thing you built the automation for.

Where SaaS still wins

Self-hosting is not free; it is pre-paid in competence. Someone has to own updates, backups and the occasional 2am restart. A team without that capability is not saving money by self-hosting, it is deferring a bill that arrives at the worst moment. For clients without an operations function, we either run the instance for them or point them honestly at the managed tier.

That is the trade in one line: SaaS sells you convenience at a price that scales with your success; self-hosting sells you a fixed bill at the price of owning the machine. After a year on the fixed bill, we know which side of that trade we want to be on.

NEXT OBSERVATIONDesign tokens that survive a rebrand↗︎