n8n Automation Cost: Hosting, Build and Maintenance Explained

The software is only one part of what you'll pay. Think of an n8n automation as three layers, and expect the plan or server to be the smallest of them.

Platform is an n8n Cloud subscription or a server you run yourself. Build is the hours to design, connect, test and document workflows. Upkeep is fixing breakages, updating n8n, renewing credentials and changing workflows as the business changes.

This guide prices each layer with live figures where they exist, and with illustrative estimates, clearly labeled, where they don't. It's written for founders and operations managers comparing n8n with Zapier or Make, or deciding whether to self-host or hire a builder.

The table below puts the three layers side by side for a simple case. The assumptions: three straightforward workflows, 30 build hours on Cloud or 35 when the builder also sets up a server, a hypothetical rate of $50 an hour, and upkeep of two hours a month on Cloud or four when you maintain the server too. Replace every number with your own.

In this example the platform is the smallest line, and self-hosting costs more overall because of the extra upkeep. Self-hosting saves money when that upkeep is cheap for you, for example because someone on staff already runs servers, or when your volume would otherwise push you onto a larger Cloud plan.

Two definitions from the n8n pricing page matter. An execution is one run of an entire workflow, no matter how many steps it has or how much data it processes. And every plan includes unlimited users, unlimited workflows and every integration. Annual billing saves 17% compared with paying monthly, and companies with fewer than 20 employees may qualify for a start-up plan at 50% off Business.

The license matters if you're an agency or a software company. n8n's license FAQ says the free Community license lets you use n8n to run your own business, build automations for clients on your instance as long as they can't create or edit them, and charge clients for setup and maintenance. It doesn't let you host n8n as a service where clients build their own workflows, let end users configure workflows through your product, or white-label n8n. Those uses need a commercial agreement.

Self-hosting removes the subscription, not the cost. n8n's own guide to choosing Cloud or self-hosting lists installation, infrastructure and maintenance as your responsibility when you self-host, and recommends Cloud for teams without technical expertise.

A typical small setup is one virtual server running n8n in Docker, a database, a reverse proxy that handles SSL, and automated backups. By default n8n stores workflows, credentials and execution data in SQLite. PostgreSQL is also supported, and it's the sensible choice once volume grows or you want the database backed up separately.

Backups need care. n8n's backup guide explains that credentials are stored encrypted, and that without the encryption key held in the .n8n folder, or a custom key you set, a restored database's credentials can't be decrypted. Back up that folder along with the database, and test a restore before you need one.

Updates never stop. n8n recommends updating self-hosted instances at least once a month, checking the release notes for breaking changes and testing on a separate instance first.

Heavier workloads use queue mode, in which a main instance receives triggers and webhooks and passes executions through Redis to separate worker instances. That means more servers and another service to monitor. Most small businesses can start without it and add it when volume demands.

Server prices in the table above come from DigitalOcean's droplet pricing, which lists basic droplets at $6, $12, $18 and $24 a month for 1 GB to 4 GB of RAM. Build costs have no equivalent public price list, because they depend on scope.

A lead-capture workflow that takes a form submission, creates a CRM record and sends a team alert is a small job. A workflow that syncs orders between Shopify, an accounting system and a warehouse, retries partial failures and reconciles every night is a project. Both show up on a quote as 'an n8n workflow'.

The effort drivers are the same across builders: how many apps are involved and whether n8n has native nodes for them or needs custom HTTP requests; the authentication type, since API keys are simpler than OAuth apps that need approval; data mapping and cleanup; error handling and retries; volume and rate limits; and documentation and handover.

For an illustrative estimate: if a lead-routing workflow takes 12 hours to scope, build, test and document, it costs $600 at a hypothetical $50 an hour or $1,200 at $100 an hour. Ask every bidder for hours as well as a price, so you're comparing effort, not only totals.

Automations break for reasons outside your control. An app changes its API or retires an endpoint, an OAuth token expires, a teammate renames a CRM field, a form gains a new question, or volume spikes past a rate limit. None of that appears in a build quote.

A recent example: Google moved offline conversion uploads to its Data Manager API in June 2026, so workflows built on the old endpoint needed rework. We explain that change in our guide to offline conversion tracking.

Build the safety net with the workflow, not after the first outage. n8n supports error workflows that run when another workflow fails; use one to alert a person with the workflow name, the failing step and the input. Keep credentials in n8n's credential store rather than pasted into nodes, and write a one-page runbook for each workflow covering what it does, what it touches and how to pause it.

Budget upkeep as a monthly block of hours or a retainer. A simple way to size it: list your workflows, rate each low, medium or high risk by how many external APIs it depends on, and reserve time for each. One or two simple workflows need very little. Each new integration adds to the total.

The three tools meter differently. n8n counts one execution per workflow run. Zapier counts a task each time a Zap successfully completes an action, and triggers don't count. Make counts a credit for each module action, such as adding a spreadsheet row or fetching an email.

As of September 2026, Zapier's Professional plan starts at $19.99 a month billed annually for 750 tasks, and Team starts at $69 a month. Make's Core plan is listed from $9 a month for 10,000 credits, with annual billing saving 15% or more. n8n Cloud Starter is €20 a month billed annually for 2,500 executions.

In the example below, Make's entry tier covers the volume, n8n's Starter covers it with room to spare, and Zapier needs a higher task tier than its entry level. Change the inputs and the answer changes. At 100 runs a month all three are cheap, and the deciding factor is who builds and maintains the workflow.

Self-hosting shifts the math again. The platform line drops to server costs, but upkeep moves from the vendor to you. n8n tends to come out ahead on total cost when you have several busy workflows, someone technical to own them, or data you'd rather keep on your own server. It tends to lose when you have a handful of simple workflows and nobody who wants to look after a server.

Quotes are only comparable if every bidder answers the same questions. Send this list with your request, and ask each builder to state their assumptions where you can't answer yet.