Reviewed September 26, 2026. Research-based review of Make's official pricing page — not a hands-on benchmark. Jet Admin publishes this comparison and is a competing product.
Make is a visual automation platform: you connect apps into scenarios and it runs them. Two things about its pricing decide most budgets, and neither is visible in the headline number.
It meters credits — one per module action — and its pricing page displays annual rates by default, so the $9 you see for Core is not the monthly price. That is $10.59.
Make review: the quick verdict
| Strong reasons to consider Make | Trade-offs to evaluate |
|---|---|
| Genuinely visual builder over 3,000+ apps | Pricing page defaults to annual; monthly is ~18% higher |
| Unlimited users on paid plans | Headline price assumes the smallest credit tier |
| Credit tiers scale from 10,000 to 8M+ a month | Free allows only 2 active scenarios and a 15-minute interval |
| Free plan has no time limit | Core, Pro and Teams include the same credits — tiers sell capability |
No numerical score is given, because we did not run a scored hands-on evaluation.
What is Make?
Make builds automations visually. You lay out modules on a canvas — fetch a row, call an API, branch on a condition — and Make executes the scenario on a schedule or a trigger. It competes most directly with Zapier and n8n.
Its distinguishing quality is the canvas itself: where Zapier presents a linear list of steps, Make shows a diagram with routers and filters. For anything with branching logic, that visual model is easier to reason about.
Make's key features
1. Credit-based metering with a concrete definition
Make's unit is the credit, and its definition is refreshingly specific: each module action counts as one credit. Adding a Google Sheets row is one credit; fetching Gmail data is one credit.
That makes estimation genuinely possible — count the modules in your scenario and multiply by runs per month. The complication is iterators: a module looping over 50 records is not one action, so loops are where estimates usually go wrong.
2. A credit slider rather than fixed tiers
You choose a monthly credit volume — 10k, 20k, 40k, 80k, 150k, 300k, 500k, 750k, 1M and upward to 8M+ — and the plan price scales with it. Every published headline price is quoted at the 10,000-credit setting.
3. Unlimited users
Paid plans include unlimited users, which is unusual for automation tools and means adding colleagues costs nothing.
4. 3,000+ app integrations plus AI tooling
The integration catalogue is large, and Make has layered AI features across all tiers: an MCP server, an AI content extractor, AI web search in beta, AI agents in beta, and an assistant called Maia. Agents can run on Make's AI provider or your own LLM key.
5. Execution controls that climb by tier
The practical ceilings move with the plan: active scenarios (2 on Free, unlimited above), minimum scheduling interval (15 minutes on Free, 1 minute on paid), maximum execution time (5 minutes on Free, 40 on paid), file size (5 MB to 1 GB) and log retention (7 to 60 days).
Make pros
The credit definition is unusually honest
"One module action, one credit" is the clearest metering statement of any tool in this review series. Compare it with platforms where an action costs "1 to 50 credits" depending on what it does — Make lets you estimate before you buy.
Unlimited users removes the worst cost axis
Across this series, per-seat pricing is the most common source of budget surprises. Make does not have it.
The visual canvas earns its keep on complex logic
Routers and filters shown as a diagram make branching automations genuinely easier to build and hand over than a linear step list.
A free plan with no time limit
1,000 credits a month, permanently, with the full visual builder and 3,000+ apps. Enough to learn the tool properly before paying.
Make cons and limitations
The pricing page shows annual rates by default
This is the detail most likely to cost you. With the annual toggle selected — the default — Core reads $9, Pro $16 and Teams $29. Switch to monthly and the same plans are $10.59, $18.82 and $34.12.
What to do: decide your billing term first, then read the prices. The annual saving is real at around 15%, but if you budget monthly figures from a page showing annual ones you will be roughly 18% short.
The headline price also assumes the smallest credit tier
Every quoted price is "for 10k credits/mo." Move the slider and the price moves. So the real entry cost is a function of two variables — billing term and credit volume — neither of which the headline number states.
What to do: count modules per scenario run, multiply by expected runs, and set the slider to that before comparing Make with anything else.
Moving up a tier buys capability, not capacity
Core, Pro and Teams all include the same 10,000 credits at the base setting. Pro adds priority execution, custom variables and full-text log search; Teams adds team roles and shared templates. Neither gives you more runs.
What to do: when you outgrow your allowance, buy a higher credit volume on your current plan rather than assuming you need a higher tier. Upgrading for throughput is the most common way to overpay here.
Iterators make estimates unreliable
Because credits count module actions rather than scenario runs, a loop multiplies consumption per run. A scenario that looks like four modules can consume far more if one of them iterates.
What to do: read actual credit consumption from the execution log rather than counting modules on the canvas. This is the single most common source of a wrong Make estimate.
The free plan is quite tightly bounded
Two active scenarios, a 15-minute minimum interval, 5-minute maximum execution and 5 MB file limit. Fine for learning, not for running anything real. Note that the 15-minute floor applies to scheduled runs — instant webhooks trigger immediately, so distinguish the two before treating it as a reason to upgrade.
What do Make users say?
We did not verify a current aggregate rating on G2 or Capterra for this review, so no score is cited. The figures above come from Make's own pricing page, read with both billing toggles.
Make pricing in 2026
Read from Make's pricing page on September 26, 2026, at the 10,000 credits per month setting, with both billing toggles checked. USD. Our Make pricing guide works through the credit formula, iterator effects and worked scenario costs in more detail.
| Plan | Monthly | Annual (monthly equivalent) | Credits | Notable |
|---|---|---|---|---|
| Free | $0 | $0 | 1,000 | 2 active scenarios, 15-min interval, 5-min execution, 7-day logs |
| Core | $10.59 | $9 | 10,000 | Unlimited scenarios, 1-min interval, API access, 5 GB transfer |
| Pro | $18.82 | $16 | 10,000 | Priority execution, custom variables, full-text log search |
| Teams | $34.12 | $29 | 10,000 | Teams and roles, shared scenario templates |
| Enterprise | Custom | Custom | Custom | On-prem agent, enterprise apps, overage protection, 24/7 support |
Annual billing saves 15% or more. Data transfer scales with credits at 5 GB per 10,000 monthly credits.
An illustrative sizing check. A scenario with 8 modules running hourly is 8 × 24 × 30 = 5,760 credits a month — inside the 10,000 tier. Add a second scenario of the same shape and you are at 11,520, which moves you to the 20,000 credit setting and a higher price on the same plan. Because credits are per module action, the cost driver is scenario complexity multiplied by frequency, not the number of automations you have.
Jet Admin vs. Make: which should you evaluate?
These are complements more often than competitors. Make moves data between systems; Jet Admin gives people an interface to work with it.
| Priority | What to evaluate |
|---|---|
| Automating data movement between apps | Make — this is its purpose |
| An interface for people to review and act on records | Jet Admin builds that over your database or API |
| Unlimited users | Both: Make on paid plans, Jet Admin on every plan |
| Predictable monthly cost | Jet Admin is flat. Make scales with credit volume |
| Complex branching logic, visually | Make's canvas with routers and filters is strong here |
| Both | A common pairing: Make for the pipes, Jet Admin for the screens |
Sources: Make pricing, Jet Admin pricing, checked September 26, 2026.
When Make is the better choice
If the job is moving and transforming data between systems on a schedule, Make does it better than an application platform will, and its visual model is a genuine strength. Jet Admin does not replace it. Make is also genuinely inexpensive at the entry tier, so the case for pairing them is about capability rather than cost.
Who should use Make — and who should compare alternatives?
Good fit: teams automating between SaaS tools; branching logic that benefits from a visual canvas; organisations with many users, since users are free; anyone who wants to estimate cost from module counts.
Compare alternatives if: you need an interface for people rather than a pipeline; your automations are simple enough that a cheaper linear tool suffices; or you need a fixed bill regardless of volume.
If what you actually need is a screen your team works in, build that in Jet Admin and keep Make for the automation.
Make review FAQ
How much does Make cost?
At 10,000 credits a month: Core $10.59 monthly or $9 annually, Pro $18.82 or $16, Teams $34.12 or $29. Free is $0 with 1,000 credits. Enterprise is custom. Prices scale with the credit volume you select.
What is a Make credit?
One module action — adding a spreadsheet row, fetching an email — counts as one credit. Count the modules in a scenario and multiply by runs to estimate, but read the execution log where iterators are involved.
Why do Core, Pro and Teams include the same credits?
Because the tiers sell capability rather than volume — execution priority, file size, log search and collaboration. Buy a higher credit volume for throughput and a higher tier for features.
Does Make charge per user?
No. Paid plans include unlimited users.
Is Make free?
There is a permanent free plan with 1,000 credits a month, but only 2 active scenarios and a 15-minute minimum interval between scheduled runs.
How does Make compare with Jet Admin?
Make automates data movement between systems; Jet Admin builds the interface your team uses to act on that data. Many teams run both.
Set the slider and the toggle before you compare
Make's published price depends on two settings the headline does not mention: your billing term and your credit volume. Work out your monthly module actions — from the execution log, not the canvas — set the slider there, pick monthly or annual, and read the number that appears.
If the automation is only half your problem, build the interface in Jet Admin alongside it.
