Pricing · 2026
Make pricing (2026): Free vs Core vs Pro vs Teams — and who should pay
Free is 1,000 credits and two scenarios. Core is the honest builder seat. Pro adds priority and log search. Teams is roles, not cheaper Core. The expensive mistake is buying the canvas because Zapier felt linear — then never naming a module.
Gregory Greenstein, Aiacent
- Published
- Updated
- Pricing verified
- 16 min read
- How we rank
Make
8.0/10Best visual automation canvas
Visual scenarios for people who will actually build the machine.
Make (the product formerly sold as Integromat) is the visual automation canvas we would hand a technical operator. Scenarios, modules, routers. You can see the machine. Zapier's simpler zap is faster to first value. Make's scenario is faster to a branching workflow you will not outgrow in month two.
- Best for
- Ops engineers who need routers, iterators, and transforms — and will maintain the scenario.
- Skip if
- You needed a simple zap this week, a self-hosted box, or Clay for a list.
Why it ranks
- Routers, iterators, and error handling that Zapier still makes you feel clever for needing
- AI modules are steps on a canvas, not a separate 'agent product' you cannot see
- Better cost control on heavy transforms if you design the scenario on purpose
Watch-outs
- The canvas is a skill. A marketer who wanted three zaps will bounce
- Not n8n — you do not own the runtime
- Easy to build an unreadable spaghetti graph and call it 'AI ops'
Product look
Make
Figure slot. No vendor screenshot until we have a rights-cleared file.
People search 'Make pricing' because they remember Integromat, or because finance asked why a visual canvas undercuts Zapier Professional on a slide. Those are different tickets. If you do not name whether you needed two scenarios to learn the diagram, a machine you will maintain, or roles for an agency, you will treat Teams as a darker Core — or stay on Free until a 15-minute interval pauses the launch.
This is a cost page, not a lab. Plan names, credit rules, and entitlements were checked against make.com/en/pricing on 19 September 2026. The vendor page still publishes Free / Core / Pro / Teams / Enterprise. The dollar figure is a credit slider, not a frozen table — confirm checkout. One August 2026 blog claimed the named tiers were gone. The page we fetched still showed them. Believe the cart. We do not invent an Enterprise sticker, an operations bake-off, or a partner URL. The full review is /tools/make. Make vs Zapier is the canvas two-way. Zapier alternatives is the leave-Zapier guide. The automation ranking is the scored desk.
Make cost in 2026, at a glance
| Plan | Public price (confirm cart) | Credits / scenarios | What you are actually buying |
|---|---|---|---|
| Free | $0 | 1,000 credits/mo; 2 active scenarios; 15-minute interval | Learn the canvas. Not a program. |
| Core | About $9/mo billed yearly / ~$10.59 monthly at 10,000 credits | Unlimited active scenarios; 1-minute schedules; Make API | The honest builder seat |
| Pro | About $16/mo billed yearly / ~$18.82 monthly at 10,000 credits | Same credit slider, plus priority execution, custom variables, full-text log search | When the wall is debug speed, not the canvas |
| Teams | About $29/mo billed yearly / ~$34.12 monthly at 10,000 credits | Roles, shared templates — the agency row | A workspace. Not cheaper Core. |
| Enterprise | Quote | SSO, enterprise apps, overage protection, 24/7 support, Value Engineering | A security and volume conversation |
- As of 27 August (Make's own FAQ on that pricing page), credits are the billing unit. Most module actions cost one credit. Error handlers and the Router cost zero. Code time is two credits per second of execution on paid plans. Some Make AI Provider modules cost more than one credit.
- A single scenario run can spend two credits or thousands. An iterator over a fat list is how Core feels 'expensive' and Zapier felt 'simpler.' Design the path.
- Free is two active scenarios, a 15-minute minimum interval, 5-minute max execution, 5 MB files, 7-day logs. Paid plans: unlimited active scenarios, 1-minute schedules, 40-minute executions. Data transfer scales at 5 GB per 10,000 monthly credits.
- Credits expire at the end of the term. Extra credits can be bought in 1,000 or 10,000 bundles, or auto-purchased in 10,000-credit packs on Core / Pro / Teams. Running out pauses scenarios; webhooks queue until credits return.
- Annual is cheaper than monthly — Make says so without publishing a static percent. Yearly Pro and Teams credits expire after 12 months instead of each month. Confirm the toggle. We will not invent a coupon.
Stay on Free if the canvas is still a test
Free is a real product after you sign up: 1,000 credits, routers and filters, 3,000+ apps, two active scenarios, a 15-minute interval. Stay here while you prove someone will open the diagram after the vendor webinar.
Leave Free the week a third scenario or a one-minute schedule is the launch, not a surprise — or the week 1,000 credits is the weekend, not a demo. Do not leave Free because a thread said 'cheaper than Zapier.' If the first job is 'Slack me when the form fires' and nobody will maintain a diagram, you are a Zapier customer. Make vs Zapier already says so.
Buy Core when the zap became a machine
Core is the honest 2026 Make builder seat. Unlimited active scenarios, one-minute schedules, the API, 100 MB files, 30-day logs. The public lead band we cite is about $9 a month billed yearly at 10,000 credits (about $10.59 month-to-month). The slider climbs — 20,000, 40,000, 80,000 and up. Confirm checkout. Size it from last month's actual module actions, not from a keynote.
Buy it when you need routers, iterators, error handling, and a canvas you can see — and someone will name the modules. That is why Make still sits second on the automation ranking (8.0) as the visual canvas. Skip Core if nobody will open the scenario after onboarding. Skip it if you needed to self-host. That is n8n, and n8n vs Zapier is the residency two-way. Skip it if the first job is three linear zaps. That is Zapier Professional — Zapier pricing is that cart.
- Best for: ops engineers and agencies who think in diagrams and will maintain the scenario
- Skip if: you needed a zap this week, a VPC, or a GTM table
- Honest watch-out: a prettier canvas will not invent a program. Make without a named module is homework.
Buy Pro when debug speed is the wall
Pro is Core plus priority scenario execution, custom variables, and full-text execution log search. The public lead band we cite is about $16 a month billed yearly at 10,000 credits (about $18.82 month-to-month). You are buying time in the log, not a darker canvas. File size climbs to 250 MB. API rate limits double versus Core.
Buy it when Core already runs and the expensive part is finding the failed bundle. Do not buy it because Core felt junior and a deck said 'advanced AI.' Mid-market teams often sign Pro and then discover they needed named modules and one owner, not priority queues on a spaghetti graph.
- Best for: builders whose scenario already ships and whose week is lost in the log
- Skip if: you have not used Core's canvas, or the leak is Zapier's catalog
- Honest watch-out: full-text search will not invent a filter you refused to name.
Buy Teams when roles, or a shared template, is the job
Teams is how Make sells the agency row. Team roles, shared scenario templates, 500 MB files, a higher API cap. The public lead band we cite is about $29 a month billed yearly at 10,000 credits (about $34.12 month-to-month). That is not cheaper Core. It is a different buying meeting.
Buy it when several people run the same machine for more than one client and a shared template is the fight. Do not buy it because Core felt lonely. The shops that stay on Core treat each client as a named scenario with one owner. The shops that move already had a spaghetti graph. The agency-stack guide is the desk around the zap.
Enterprise is a quote — and credits are still the meter
Enterprise is SSO, enterprise apps (Workday, ServiceNow, and the rest of Make's exclusive list), custom functions, overage protection, 24/7 support, Value Engineering, 60-day logs, 1,000 MB files. You talk to sales. We will not guess a sticker. If you are asking whether Make is worth $9, you are not an Enterprise buyer yet. Prove Core first.
Core vs Zapier Professional, as a bill
Core's public 10,000-credit band commonly undercuts Professional's 750-task band. On the job, a sloppy iterator or a chatty Zapier AI step will erase the savings. Compare the graph you will keep on, not the homepage numeral. Zapier pricing is the other cart. Make vs Zapier is the winner-by-job. Is Make worth it is the subscription sibling of this page.
What we are not pricing
- An Enterprise quote. Anyone who publishes one invented it.
- A frozen dollar table. Make's public page is a slider. The $9 / $16 / $29 yearly lead bands are the cart we checked on 19 September 2026 at 10,000 credits — confirm checkout.
- A 2024 'operations' story. Credits replaced operations. Articles that still quote operations-only math are stale.
Most 'what does Make cost' tickets are a Core ticket, a Teams ticket, or a Zapier Professional ticket. The pricing page is doing too much work if you have not named the machine.— Aiacent pricing, 2026
Verdict
One builder, a scenario you will name and keep: Core at the credit band you actually burn, annual if that already survived Free. Debug speed or custom variables: Pro. Agency roles and shared templates: Teams. One person proving they will open the diagram: stay on Free, then leave if two scenarios is still homework. Three linear zaps: do not buy Make to feel technical — Zapier pricing and Make vs Zapier. Graph you will host: n8n vs Zapier. Trying not to buy Zapier at all: Zapier alternatives. Then read is Make worth it if the fight is the subscription, and the automation ranking if you want the score next to Zapier and n8n.