Make vs n8n is decided by how each one bills. Make charges a credit for every module action, so short scenarios are cheap and long or looping ones add up. n8n charges one execution per full run and can be self-hosted for free. On a five-step lead-routing scenario the two are close on entry plans; n8n pulls ahead as steps, items and volume grow. Pick Make for ease and no servers, n8n for long workflows, code, AI agents and control.
Make vs n8n comes down to the billing unit and who runs the server: Make charges one credit for every module action and is hosted only, while n8n charges one execution for a whole workflow run and can be self-hosted for free. Pick Make for short scenarios built by non-technical people; pick n8n for long workflows, loops over many items, code, AI agents or anything that has to run on your own infrastructure.
Updated 11 October 2026. A documentation-based comparison: costs below are arithmetic on published prices, not measured bills. Checked against Make's pricing page, Make's help center on credits, operations, extra credits, changing a subscription and its plan adjustments, Make's own Make vs n8n page, the n8n pricing page, n8n's docs on how executions count and its execution-limit article. Make prices are in US dollars and n8n's in euros; we do not convert between them.
This page replaces our April 2026 version, which called n8n open source and walked through steps we could not verify. The rebuilt version does one job: it takes a single lead-routing scenario, counts what each platform would bill for it, and shows where the answer flips. It is part of our n8n hub; for the three-way view with Zapier, see n8n vs Zapier vs Make.
Make vs n8n: the verdict
- Marketing or ops staff build and own the automations
- Most scenarios have a handful of modules
- Triggers are instant webhooks, not constant polling
- Nobody should ever maintain a server
- You want a permanent free plan to learn on
- A low entry price matters more than the price at scale
- Workflows have many steps, branches or sub-workflows
- One run processes dozens or hundreds of items
- You want JavaScript or Python in the flow at no extra charge
- You build AI agents with tools, memory and MCP
- Data must stay on infrastructure you control
- Volume is high and someone can run Docker
Make.com vs n8n head to head
| Make | n8n | |
|---|---|---|
| Billing unit | Credits: one per module action, per bundle; AI and code modules can use more | Executions: one per full workflow run, however many steps |
| Free option | Free plan: 1,000 credits a month, 2 active scenarios, no time limit | Self-hosted Community Edition; 14-day Cloud trial with 1,000 executions |
| Entry paid plan | Core: $9 a month for 10,000 credits, per Make's comparison page | Cloud Starter: €20 a month billed annually, 2,500 executions |
| Hosting | Make's cloud only | n8n Cloud (data in Frankfurt) or your own server |
| Licence | Proprietary | Sustainable Use License (source-available) |
| Shortest schedule | 15 minutes on Free, 1 minute on paid plans | Schedule Trigger intervals down to seconds |
| Longest single run | 5 minutes on Free, 40 minutes on paid plans | 180 seconds on the Cloud trial; your own setting when self-hosted |
| Custom code | Make Code App: 2 credits per second of run time | Code node inside the same execution, no extra charge |
| AI | Make AI Agents (beta), AI Toolkit, MCP server | AI Agent node with model, memory and tool sub-nodes; MCP nodes |
| Out of quota | The scenario ends with an error and its scheduling is disabled, unless you buy extra credits | New runs fail with "Execution limit reached" until the calendar month resets or you upgrade |
| Users | Team roles on the Teams plan | Unlimited users on every plan; admin roles from Pro |
Limits come from the plan comparison on Make's pricing page and the n8n pricing page, both read on 11 October 2026. The out-of-quota row is worth a second look before you put anything customer-facing on either: Make's error reference says running out of credits is a fatal error that disables the scenario's scheduling, and n8n's support article says over-limit executions "are not queued".
Make vs n8n pricing: credits vs executions
Make renamed its billing unit from operations to credits, and its help center keeps the rule simple for ordinary apps: one operation equals one credit. An operation is a single module run, and a module runs once for every bundle of data it receives. Three details shape the bill:
- The trigger always costs one. A trigger module uses one credit each time it runs, whether it returns fifty records or none. A polling trigger on a 15-minute schedule is 96 checks a day, about 2,880 credits a month, before any work is done.
- Routers and filters are free. Make's docs state that routers do not consume credits, and its Academy course says the same of a bundle passing a filter.
- AI and code cost more. Make's built-in AI provider is charged by tokens, and the Make Code App is listed at 2 credits per second of run time.
n8n counts executions. Its pricing page defines one as "a single run of your entire workflow", and its docs add the fine print: a Schedule Trigger counts every time it fires, a webhook counts once per request, a polling trigger counts only when it finds new data, and manual test runs, sub-workflows and error workflows do not count at all.
- 01Webhook receives the lead
Make: 1 credit for the trigger. n8n: the execution starts.
- 02Search the CRM for the email
Make: 1 credit.
- 03Route: new or existing, hot or cold
Make: 0 credits. Routers and filters are free.
- 04Create or update the contact
Make: 1 credit.
- 05Alert the owner or add to nurture
Make: 1 credit, whichever branch runs.
- 06Log a row in the sheet
Make: 1 credit. Totals: 5 Make credits, 1 n8n execution.
Counting rules from Make's help center and Academy and from n8n's docs, checked October 2026.
The same lead-routing scenario at 1,000, 10,000 and 100,000 leads
Five credits against one execution, multiplied out. The scenario is real in shape and illustrative in volume: nobody ran it for this article, and your own module count is what matters.
Units, not money: a credit and an execution are priced very differently. Source: arithmetic from the counting rules in Make's help center and n8n's docs, checked October 2026
| Leads a month | Make credits | Make bill | n8n executions | n8n Cloud bill |
|---|---|---|---|---|
| 1,000 | 5,000 | $9 a month: the entry paid plan covers it | 1,000 | Starter, €20 a month billed annually (2,500 included) |
| 10,000 | 50,000 | Between the 40,000 and 80,000 slider stops. At Make's two published per-credit rates, about $38 to $45 of credits | 10,000 | Pro, €50 a month billed annually (10,000 included, so no headroom) |
| 100,000 | 500,000 | $338.13 a month: the 500,000-credit monthly example in Make's help center | 100,000 | Above the listed tiers. Larger Pro subscribers on monthly billing can add executions, up to 500,000 a month |
Where the Make figures come from: the $9 entry price for 10,000 credits is on Make's comparison page (checked 15 October 2026); the help center's extra-credits article works through "a $9 plan with 10,000 credits", its subscription article prices Core at $113.85 for 150,000 credits a month, and its plan-adjustment notice gives $338.13 for 500,000. That makes the published per-credit rate $0.0009 at the bottom and about $0.00076 at 150,000. The 50,000 row is our arithmetic between those two rates, because the slider price is not in the page text; read it off the slider before you budget.
The honest reading is that this scenario does not favour n8n Cloud. At 1,000 leads Make is $9 against €20. At 10,000 the two are close. n8n's decisive number is the one missing from the table: self-hosted, the Community Edition runs all three volumes for the price of a server. Our breakdown of what self-hosted n8n really costs puts a small instance with backups at about $14 a month before your time, and you would size up for the largest row.
Where the math flips
Divide each entry plan by its allowance and you get a price per unit. n8n Cloud Starter works out at €0.008 per execution and Pro at €0.005. A Make credit is $0.0009 on the 10,000-credit plan. So a run has to use roughly six to nine credits before n8n Cloud is the cheaper place for it, setting the currency gap aside. Three things push a scenario past that line quickly:
- Bundles. Every item a module processes is a credit. Make's own help page shows a run going from 11 operations to 3 once a Text aggregator combines ten contacts into one email.
- Polling. Checking a mailbox or a sheet every few minutes spends credits whether or not anything arrived. n8n does not count empty polls.
- Length. Enrichment, deduplication, two notifications and a log row add a credit each in Make and nothing in n8n.
Make in 2026: plans, strengths and limits
Make is the easier tool to hand to someone who has never automated anything. Scenarios are built from app modules on a canvas, the free plan never expires, and there is no server anywhere in the picture.
| Plan | Credits | What changes |
|---|---|---|
| Free | 1,000 credits a month | 2 active scenarios, 15-minute minimum interval, 5-minute runs, 5 MB files |
| Core | Slider, up to 300,000 credits | Unlimited active scenarios, 1-minute interval, 40-minute runs, 100 MB files, Make API |
| Pro | Slider, up to 8 million credits | Adds priority execution, custom variables, full-text log search, 250 MB files |
| Teams | Slider | Adds teams and team roles, shared scenario templates, 500 MB files |
| Enterprise | Custom | Adds custom functions, enterprise apps, overage protection, 60-day logs, 1,000 MB files |
A note on what you will see. Make's pricing page sets each price with a credit slider, and the price is not in the page text. Make's own comparison page lists Core at $9, Pro at $16 and Teams at $29 a month, each starting at 10,000 credits (checked 15 October 2026), without saying whether that is the monthly or annual rate. Trust the plan names and the price at your own checkout over any list, including this one.
- Strengths. More than 3,500 apps in its integrations directory (checked 15 October 2026), routers and filters at no credit cost, sub-scenarios, and a 40-minute run limit on paid plans.
- Limits. No self-hosting. Extra credits cost 25% more than plan credits. Every loop and every poll is metered. The free plan allows two active scenarios and a 15-minute schedule.
n8n in 2026: plans, strengths and limits
n8n is the tool for people who are comfortable seeing their data as JSON. Every Cloud plan includes unlimited users, unlimited workflows and every integration; what you buy is executions and concurrency.
- Cloud Starter: €20 a month billed annually, 2,500 executions, 5 running at once.
- Cloud Pro: €50 a month billed annually, 10,000 executions, with admin roles and workflow history.
- Business: €667 a month billed annually. It is a licence for a self-hosted instance, with SSO, environments and Git version control.
- Community Edition: free to self-host, no execution cap.
Prices checked October 2026; the n8n pricing guide covers every tier and what counts as an execution. The limits are the mirror image of Make's. There is no permanent free Cloud plan. Runs over the monthly quota fail instead of waiting. And the editor expects you to understand items, expressions and the occasional API document.
Self-hosting: the option only n8n has
Make runs on Make's servers on every plan. n8n's Community Edition runs wherever you put it, which is why teams with data-residency rules or very high volume end up there. Two cautions before you count it as free. The licence is source-available, not open source: you may run your own business on it and build automations for clients, but not host it as a service where clients build workflows. And the server is yours to patch, back up and upgrade. n8n's 3.0 breaking-changes page says self-hosted 3.0 requires a Docker-based deployment; on 11 October 2026 the newest stable release was still 2.42.6.
AI steps and agents on each
Both platforms now treat AI as a core feature, and both bill it differently from ordinary steps.
- Make. Make AI Agents (in beta), an AI Toolkit and an MCP server are on the pricing page. With Make's own AI provider you pay credits based on tokens. With your own OpenAI or Anthropic connection, open to all paid plans since November 2025, you pay Make per operation and the model provider for tokens.
- n8n. The AI Agent node takes a chat model, memory and tools as sub-nodes. One agent turn is one execution however many tool calls it makes, and tokens are billed by your model provider. Self-hosted, an Ollama Chat Model node can point at a model running on your own machine.
On either one, the model bill usually outgrows the platform bill. Our LLM API pricing comparison has current per-token rates.
Price your own scenario before you choose
- 1Write down every module in one run
Skip routers and filters. Count the trigger as one.
- 2Multiply by items per run
Each module after the trigger runs once per bundle. Ten rows through three modules is 30 credits.
- 3Add polling checks
Checks a day times 30, for every scenario that polls. Instant webhooks only cost when they fire.
- 4Multiply by runs a month
Expected result: your Make credits. Add 20% headroom.
- 5Count trigger firings
Expected result: your n8n executions. Empty polls, test runs and sub-workflows are not counted.
- 6Put both against the price lists
Then add the server and your time if n8n would be self-hosted.
If the two totals land close, choose by who will maintain the automations. A cheaper tool that only one person can read is the expensive option the month that person is away.
Alternatives if neither fits
- Zapier bills per successful action and lists the widest app catalogue. See Make vs Zapier and n8n vs Zapier; if you are leaving it, the Zapier to n8n migration guide has the node mapping.
- Activepieces counts one credit per run like n8n and has an MIT-licensed core. It is one of twelve options in n8n alternatives.
- A side-by-side spec sheet of the two tools on this page is at n8n vs Make.
And if the scenario you are pricing is turning into something customers would pay for, that is a product, not an automation. The AI SaaS Builder program has no Make or n8n lessons; it covers building the product itself, with Supabase for data and auth, the Claude API for the AI feature, deployment on Vercel and Stripe billing.
Make vs n8n: FAQ
Is Make or n8n better?
Make is better when non-technical people build the automations, scenarios are short, and nobody wants to run a server: it is hosted only and its entry plan is $9 a month. n8n is better when workflows are long, loop over many items, need code or AI agents, or must run on your own infrastructure. The billing units decide most cases: Make counts each module action, n8n counts each full run.
Is n8n cheaper than Make?
It depends on the length of the workflow. On published entry prices, checked 15 October 2026, a Make credit costs about $0.0009 on the $9, 10,000-credit Core tier and an n8n Cloud Starter execution about €0.008. A run of roughly six to nine module actions costs about the same on both; shorter runs favour Make and longer ones favour n8n. Self-hosting the free n8n Community Edition removes the per-run price entirely.
How do Make credits compare with n8n executions?
A Make credit is charged each time a module runs: once for the trigger and once per module for every bundle it processes. Routers and filters are free, and AI and code modules can cost more. An n8n execution is one complete run of a workflow, whatever the number of steps or items. A five-module scenario is five credits in Make and one execution in n8n.
Can you self-host Make?
No. Make is a hosted service on every plan; its own comparison page calls it cloud-first at all subscription levels. Its pricing page lists an on-prem agent for reaching systems inside a local network, but the scenarios still run on Make's servers. If the automation engine itself must run on your hardware, n8n's Community Edition is the option in this pair.
Is n8n really free?
The self-hosted Community Edition has no licence fee and no execution cap, under n8n's Sustainable Use License. You pay for a server and your own time on updates and backups. n8n Cloud has a 14-day trial with 1,000 executions and no card, then paid plans from €20 a month billed annually. Make, by contrast, has a permanent free plan with 1,000 credits a month.
Which is easier for beginners, Make or n8n?
Make. There is nothing to install, its free plan has no time limit, and scenarios are built by picking app modules and mapping fields. n8n asks for a little more: you see the data as JSON, expressions use JavaScript syntax, and self-hosting adds server work. A beginner who is comfortable reading API documentation will be fine with either.
Can I use Make and n8n together?
Yes. Both can send and receive webhooks, so a Make scenario can call an n8n workflow and the other way round. A common split is Make for small scenarios that business users own, and n8n for long, high-volume or AI-heavy workflows. Count the cost on both sides: the hand-off is one credit in Make and starts one execution in n8n.
Free · no card needed
Start with the free Starter Kit.
A unit economics calculator from AI SaaS Builder, plus four more working files.
Priced the automation? Price the product next.
When a scenario starts doing work customers would pay for, AI SaaS Builder, included in All Access, covers building it as an app: Supabase for data and auth, the Claude API for the AI step, Vercel to deploy and Stripe to charge. It has no Make or n8n lessons. The other three programs, weekly coaching and the community come with the same subscription.
Stuck between Make and n8n?
Post your module count and monthly runs in the free Discord and compare bills with people running both.