Make vs n8n pricing.
Count the work, not just the monthly fee.
Make charges around credits consumed by scenario activity. n8n Cloud prices around complete workflow executions. The cheaper option depends on how many items and steps each run processes.
For: anyone choosing between Make and n8n for a real monthly workload, not a feature checklist.
You will learn: the current entry prices, what each platform counts, and when a longer workflow can change the result.
Prepare: monthly starts, items per start, actions or steps per item, retries, and expected maintenance time.
Next: run the same synthetic workflow for at least seven days, then compare the recorded credits and executions.
Disclosure: Some sign-up links may pay AUTOMATION NOTE a referral fee at no added cost to you. Prices were checked on 20 August 2026. Confirm tax, currency, billing period, and cancellation terms before paying.
The short answer
Start with Make when the job is a short SaaS-to-SaaS flow and a non-technical maintainer benefits from its visual interface. Start with n8n Cloud when one run contains many steps, code, or complex branches. Choose self-hosted n8n only when someone will own updates, monitoring, backups, and recovery.
Those are starting points, not price guarantees. Measure one representative workflow before choosing a paid plan.
Current entry prices
On a phone, scroll the table sideways to see the billing unit.
| Product and plan | Displayed price | Included usage | Main unit |
|---|---|---|---|
| Make Free | $0/month | 1,000 credits/month | Scenario activity such as module actions |
| Make Core | $10.59 monthly, or $9/month equivalent billed annually | 10,000 credits/month | Scenario activity such as module actions |
| Make Pro | $18.82 monthly, or $16/month equivalent billed annually | 10,000 credits/month | Scenario activity such as module actions |
| n8n Starter | €20/month equivalent, billed annually | 2,500 executions/month | Complete workflow executions |
| n8n Pro | €50/month equivalent, billed annually | 10,000 executions/month | Complete workflow executions |
Make prices above use the 10,000-credit tier. Annual figures are monthly equivalents paid on an annual billing cycle. n8n figures are also monthly equivalents billed annually. Do not compare them as if the billing commitments were identical.
Why the billing unit changes the answer
Assume a Make scenario consumes four credits for each processed item. At 1,000 items per month, that is about 4,000 credits. If the same job consumes sixteen credits per item, it reaches about 16,000 credits and passes the 10,000-credit tier.
For n8n Cloud, a workflow that starts 1,000 times is generally counted as 1,000 workflow executions even when more steps sit inside that workflow. Separate workflow calls, retries, and batch design can change the total, so inspect the execution history rather than relying on this example alone.
What the estimate leaves out: Make usage can change with bundles, polling, AI features, Code, and retries. n8n usage can change with sub-workflows, retry design, and how items are batched. External AI APIs and other SaaS subscriptions are separate costs.
Choose from the shape of the workflow
- Try Make first: a short flow, a few SaaS apps, visual maintenance, and predictable item volume.
- Try n8n Cloud first: many steps per start, code, complex branching, or n8n-specific nodes.
- Consider self-hosted n8n: you need control over the runtime and already have an owner for security updates, monitoring, backups, and recovery.
If you are still deciding what belongs in Cowork, Make, or n8n, use the workflow boundary comparison first. For the Japanese version of this guide, see Makeとn8nの料金比較.
Test before paying
- Use synthetic data and build one representative workflow.
- Run it for at least seven days, including ordinary failures and retries.
- Record Make credits or n8n workflow executions.
- Project the result to one month and add maintenance time.
You can also put setup cost and saved time into the automation ROI calculator. It runs in the browser and does not send the entered values.
Turn one defined flow into a working scenario.
A written, fixed-scope Make build covers up to 10 main modules and three connected apps from USD 950. No call is required. Scope and acceptance conditions are confirmed before payment.
See the Make build scopeOfficial sources
Questions people ask before choosing
Is n8n always cheaper for a long workflow?
No. Its execution-based pricing can help when many steps run inside one workflow, but sub-workflows, retries, hosting, and maintenance still affect the total.
Is self-hosted n8n free?
The Community Edition is available for self-hosting, but the server, updates, monitoring, backups, recovery, and operator time still have a cost. Check the license against your intended use.
Can I choose from the published prices alone?
No. Use the prices to choose a test, then use your own recorded usage to choose a plan.
Checked scope
This page contains affiliate advertising. The listed plan prices, billing units, and free or trial entry points were checked on 20 August 2026. Taxes, exchange rates, add-ons, and your final checkout total were not measured.
Published and checked: 2026-08-20