n8n vs Zapier vs Make: Which One Go Save You Money?
Zapier and Make dey bill per task, but self-hosted n8n na flat server cost. Use real monthly volume find the crossover, then check n8n license terms.
The one difference wey decide this
n8n, Zapier and Make dey do the same work. Trigger go fire, data go move between APIs, and something go land for another system. The choice between dem usually depend on one thing: the billing unit. Zapier and Make charge for every unit of work wey your automations perform. Self-hosted n8n no charge anything per unit of work, because na server you dey pay for instead.
Na this one difference dey drive everything wey follow. Metered plan fit cost almost nothing when you run ten workflows per day, but e fit become your biggest software cost when workflow start firing every minute. Flat server cost dey do the opposite: e fit look expensive on day one, but e no dey increase as volume grow. No be any of the two models dey deceive person. Dem just bill different users better.
Wetin each product really dey charge for
Zapier dey bill per task. Zapier own definition be say task na when Zapier successfully complete one unit of work. Each successful action step for one Zap dey use one task, and some actions dey use more than one. Triggers and polling no dey count, failed actions no dey count, and the built-in tools (Formatter, Paths, Filter, Delay, Looping, Storage) no dey count. So, if one Zap get one trigger and three action steps, e go cost three tasks every time e run. As of October 2026, the free tier get 100 tasks per month, while the paid Professional plan start around 20 US dollars per month when dem bill yearly ($19.99), for 750 tasks.
Make dey bill per credit, wey na the unit wey e used to call operation before. Make help center talk say every time one module for one scenario perform action, e dey use credits, and by default one operation equal one credit. Module dey run once for every bundle wey e receive, and na this part you need watch: if one module loop through 200 rows, e go spend roughly 200 credits, no be one. As of October 2026, the free tier get 1,000 credits per month. For July 2026, the Core plan start around 12 US dollars per month for 10,000 credits. Make pricing page dey load prices dynamically, so check the billing toggle there to see today's figure.
Self-hosted n8n no dey charge anything per execution. The Community edition free and e carry almost the complete feature set. Workflow runs, nodes inside one run, loop iterations and retries all cost zero, because the only meter na your server CPU, memory and disk. Paid self-hosted tiers dey available and dem need license key, and dem dey meter volume. As of October 2026, n8n pricing page list the self-hosted Business plan at 667 euros per month, billed yearly, for 40,000 workflow executions. One execution na one run of the whole workflow, no matter how many steps e get. Extra buckets of 300,000 executions cost 4,000 euros. The key dey ping n8n license server every day. The ping include the number of production executions, and usage from every instance wey share the key dey count toward the quota. Those tiers also sell governance features like single sign-on and separate environments, but throughput dey part of the bill for dem. If you don already set up n8n for VPS with Docker and HTTPS on the Community edition, you don already pay the complete recurring bill.
The install command from n8n own docs short enough to show the point:
docker volume create n8n_data
docker run -it --rm \
--name n8n \
-p 5678:5678 \
-e GENERIC_TIMEZONE="Europe/Berlin" \
-e TZ="Europe/Berlin" \
-e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \
-e N8N_RUNNERS_ENABLED=true \
-v n8n_data:/home/node/.n8n \
docker.n8n.io/n8nio/n8nThe editor then dey respond on port 5678. That command na only for first look, because e dey use the default SQLite file and --rm dey throw away the container when you stop am. For server wey you depend on, use Postgres and put reverse proxy for front.
A realistic month, wey you count
Vague comparisons no useful, because the answer depend completely on your volume. So count am. Na four automations be these wey small company really dey run, together with how often each one dey fire and how many billable steps each run dey perform.
Di data wey dey behind dis chart
[
{
"label": "Form to CRM to Slack",
"runs_per_month": 1200,
"billable_steps": 3,
"units_per_month": "3,600"
},
{
"label": "Order sync, every 15 min",
"runs_per_month": 2880,
"billable_steps": 4,
"units_per_month": "11,520"
},
{
"label": "AI inbox triage",
"runs_per_month": 900,
"billable_steps": 5,
"units_per_month": "4,500"
},
{
"label": "Daily revenue report",
"runs_per_month": 30,
"billable_steps": 6,
"units_per_month": "180"
}
]The order sync alone dey spend 11,520 billable units every month, because schedule trigger wey dey run every 15 minutes fires 2880 times and each run dey touch 4 paid steps. The daily report, wey feel like the heavy workflow because e get the most steps, dey spend 180. Frequency dey beat complexity every time. Na why estimating from the shape of workflow instead of the schedule dey make people receive invoice wey dem no expect.
Together, those four automations dey spend 19,800 billable units every month. For Zapier, that one put you for 20,000-task tier of paid plan. For Make, na roughly twice the credits wey Core plan include, so you go need buy higher plan. For self-hosted n8n, na the same monthly server bill as running one workflow, and the server no go notice.
Now change one number. Move the order sync from every 15 minutes to every 5 minutes. Zapier and Make go triple that line to 34,560 units, and the invoice go move to the next tier. The n8n box go add only few percent CPU. That difference, instead of the headline price of any plan, na the real decision.
Where the crossover dey
No universal break-even point dey, but the pattern dey predictable.
- Below roughly 1,000 units per month, hosted free tiers win completely. Nothing beat zero cost, and you no get server to patch.
- Between roughly 1,000 and 10,000 units, Make entry plan still cheap. For July 2026, its Core plan cover 10,000 credits for about 12 dollars per month, so hosted tool still give better value for that range. Zapier price dey rise much faster for the same range. As of October 2026, its Professional plan, when billed yearly, cost $19.99 per month for 750 tasks, $49 for 2,000, $89 for 5,000 and $129 for 10,000. So near the top of the range, Zapier bill don already pass the cost of small server plus your own attention.
- Above roughly 20,000 units per month, metered billing dey add up, and fixed server cost normally win. E go continue to win as volume dey increase.
- Any workflow wey dey process rows one after another, like CSV import, list of 500 orders, or paginated API, dey skip those ranges completely. One run fit use thousands of units.
Na this last case make self-hosting stop to be just preference. Nightly job wey dey process 5,000 records go use 5,000 credits for metered plan, but e go use only CPU for one execution on n8n.
The same logic apply to AI steps, because na there automation volume dey grow fastest. Every model call inside hosted scenario na billable unit on top of the model provider own token charge. So dem dey meter you twice for the same work. Running the Claude API inside n8n workflows mean say na only the model provider you go pay.
n8n license, plain talk
n8n no be open source under the usual definition, and if person pretend say e be, na later surprise go follow. E dey ship under Sustainable Use License, wey talk say:
You fit use or modify the software only for your own internal business purposes or for non-commercial or personal use.
And about passing am to other people:
You fit distribute the software or provide am to other people only if you do am free of charge for non-commercial purposes.
Compare this with wetin you plan to do. If you run n8n to automate your own company work, na internal business purposes, and dem allow am. This cover almost everybody wey dey read this. But if you run n8n as the engine behind product wey you dey sell, or resell hosted n8n instances to customers, the free license no cover am. You go need commercial agreement with n8n. Check the current LICENSE.md for the n8n repository before you build business on top of am, because terms fit change and na only the text for the repository count.
Another smaller catch dey. The free Community edition get almost every feature, and free registration unlock a few more, like folders and debug in editor. Features for bigger teams, including single sign-on, log streaming, and separate environments, dey behind paid license key. Those ones na governance features, but the paid key also limit workflow executions (40,000 per month for the self-hosted Business plan as of October 2026). The free Community edition no get that limit. If you no sure which side of that line a feature you depend on dey, make you go through the community and enterprise limits feature by feature before you design around one.
Wetin the flat server cost no cover
The honest version of the self-hosting argument include the parts wey no free.
Uptime na your responsibility. When hosted platform get outage, you go wait while somebody else dey paged. When your VPS get outage, na you go fix am, no matter the hour wey e happen. Upgrades na your responsibility, because n8n releases often and container image wey you never update fit become security problem. Backups na your responsibility: the n8n encryption key and Postgres database together na the only copy of your credentials and workflows, and if you lose the key, every stored credential go become unreadable. Point encrypted restic backups at both from the first day, no be when first incident happen. To keep the editor away from public internet na another job wey move come you, and for company, e no free. Tailscale free Personal plan cover up to six users, but Tailscale talk say na only for non-commercial use, so team wey dey secure company n8n box need Standard plan, wey cost $8 per user per month as of October 2026.
You still dey responsible for the parts wey hosted plan quietly include. Zapier and Make maintain thousands of app connectors and repair dem when vendor change API. n8n get large node library and generic HTTP node wey cover the rest, but when integration spoil, na your afternoon e go take. Hosted plans still include compliance paperwork, support with response time, and another person’s on-call rotation.
Budget the real number honestly: the server, plus about one hour maintenance every month, plus the day wey you go spend for initial setup. If that total still lower than metered invoice, self-hosting na the right choice. For 19,800 units every month, e usually dey. For 500 units every month, e usually no dey.
Which one you suppose pick
Pick Zapier when na connector list be the main product. E get the widest app coverage and e easy to learn, and if your automations short and no dey happen often, per-task billing truly cheap.
Pick Make when your logic dey visual and dey branch. Its canvas handle routers, iterators and error handlers well, and its credits cost less per unit than Zapier tasks for similar tiers. Watch the iterators, because na there credit usage fit grow without warning.
Pick self-hosted n8n when volume high, when data no fit leave your own infrastructure, or when workflows dey call models and databases wey you already run. Na only this one among the three wey let you read the code path wey workflow dey follow and change am. Budget one VPS and one hour every month, and read the license first. E deserve place for any 2026 shortlist for self-hosting because of the reason above: the meter stops.
FAQ
Self-hosted n8n really free?
Community edition free to run, and e no get per-execution charge. E get almost all the features. You still go pay for the server. Features wey larger teams need, like single sign-on, log streaming, and separate environments, need paid license key. For Community edition, nobody dey measure your workflow volume. Na this be the main reason to self-host. Paid self-hosted plans dey different. As of October 2026, Business plan get 40,000 executions every month, and extra executions dey billed in groups of 300,000.
How many Zapier tasks one Zap dey use for each run?
One task for each successful action step, but some actions cost more than one. Trigger free, polling free, failed actions free, and built-in tools like Formatter, Paths, Filter, and Delay free. So, Zap wey get one trigger and three actions go cost three tasks for each run. If e run 1,000 times for one month, e go use 3,000 tasks.
Make credits and Zapier tasks dey count the same way?
Dem similar, but dem no exactly the same. Both charge for each action wey workflow perform. Make counts every module run as one credit. This one include transformation modules and every iterator pass. Zapier no charge for im built-in formatting and filtering tools. The difference dey matter most for workflows wey loop through lists, because Make dey add charge for every iteration quickly.
I fit use self-hosted n8n inside commercial product?
No, not under the free license. Sustainable Use License allow you use am for your own internal business work, or for non-commercial or personal use. Automating work for your own company dey allowed. But if you embed n8n inside product wey you sell, or resell hosted instances, you need commercial agreement with n8n. Read the current LICENSE.md for the repository before you commit to a design.
For what volume I suppose switch from Zapier or Make to n8n?
No fixed number dey, but the general pattern clear. Below about 1,000 billable units every month, hosted free tiers usually better. Above about 20,000 every month, fixed server cost usually better. Zapier become expensive before Make within that range, because 10,000 tasks cost $129 every month on im yearly Professional plan as of October 2026. Any workflow wey iterate over rows fit break this rule immediately. One run over 5,000 records go use 5,000 units for metered plan, but e no go add extra cost for your own server.