Make pricing calculator: which plan and how many credits?
Estimate credits from real scenario runs instead of guessing from list price. The result uses only the Make tiers stored from the public pricing source; above 10,000 credits it tells you to verify the current vendor price.
We may earn a commission if you buy through links on this page, at no extra cost to you. Our verdicts are based on the data shown.
Runs × billable modules × overhead
A standard module run generally consumes a credit. Iterators, retries and variable-credit AI features can lift usage, so add headroom rather than treating a successful happy-path run as the whole month.
Link copied.
Make plan limits stored by StackPick
| Plan | Monthly equivalent | Published capacity stored | When it fits |
|---|---|---|---|
| Free | Free | 1,000 credits | 1,000 credits/month; 2 active scenarios |
| Core | $9.0/mo | 10,000 credits | 10,000 credits, unlimited active scenarios |
| Pro | $16.0/mo | 10,000 credits | Priority execution, custom variables, full-text logs |
Monthly amounts reflect the billing cadence described in the tool record. Taxes, regional pricing, credit add-ons and checkout promotions are excluded. Check Make pricing directly.
Four workload examples
| Workflow | Monthly runs | Billable modules/run | 10% headroom | Calculated credits | Likely stored tier |
|---|---|---|---|---|---|
| Lead form → CRM → email | 100 | 3 | 30 | 330 | Free, if ≤2 active scenarios |
| Order → sheet → Slack → invoice | 500 | 4 | 200 | 2,200 | Core |
| Daily enrichment pipeline | 1,000 | 7 | 700 | 7,700 | Core or Pro by features |
| High-volume operations | 5,000 | 5 | 2,500 | 27,500 | Check current vendor pricing |
Free vs Core vs Pro: the decision rule
Use it to validate one or two small scenarios
The stored Free tier covers 1,000 credits and two active scenarios. It is a test environment, not a safe default for a business-critical automation near the limit.
Use it when capacity is the main requirement
Core is the lowest stored paid tier with 10,000 credits and unlimited active scenarios. It is the calculator default when Free limits are exceeded and Pro-only features are not selected.
Use it when execution and debugging features matter
Pro shares the stored 10,000-credit capacity but adds priority execution, custom variables and full-text logs. The plan choice is therefore feature-led, not a larger credit bucket in this dataset.
Costs people miss in a Make estimate
- Iterators: one input can fan out into many module operations.
- Retries and errors: failed or repeated modules consume headroom.
- Variable-credit AI features: a simple “one module = one credit” rule may not hold.
- Migration and testing: dual-running old and new scenarios temporarily raises usage.
- Feature fit: the cheapest capacity tier can still be wrong if logs or variables are required.
For a platform-neutral comparison, run the workflow automation cost calculator. For execution pricing and self-host operations, see n8n vs Make.
Get Make price-change alerts
We email only when a tracked published price or stored capacity changes.
Saved. We will email only for verified changes.Could not save. Try again.FAQ
How does Make count credits?
For standard scenarios, a billable module run generally consumes a credit. Iterators, retries and some AI features can change actual usage. The calculator makes this uncertainty explicit through the overhead input.
Is the Make Free plan enough for a small business?
It can validate low-volume scenarios, but the stored tier is limited to 1,000 credits and two active scenarios. A production workflow near the limit has little retry headroom.
Why does the calculator stop pricing above 10,000 credits?
That is the largest capacity stored in the verified tool record. Rather than multiply a list price linearly, StackPick sends you to the current vendor source.
Does StackPick earn from Make?
The Make CTA is an affiliate route and may generate a commission. Commission never changes the credit calculation or plan rule; see how we make money.