Visual scenario builder billed in credits, where one module action on one bundle is one credit; routers, filters and error handlers cost nothing.
Teams that want a visual canvas with per-branch routing and heavy field-level data mapping across 3,000+ apps, where routers, filters and error handlers consume no credits so complex branching stays cheap. The $9/mo entry point with a slider to 8M+ credits suits teams scaling gradually from one scenario to hundreds. The 1-minute minimum scheduling interval on paid plans fits near-real-time operational automations.
Credits replaced operations as Make's billing unit, and the unit is the module run per bundle, not the scenario run. Make's help centre is explicit: a trigger that finds five emails costs one credit, but a downstream Add a Row action then performs five operations and consumes five credits, so iterating over arrays multiplies cost in a way scenario counts never reveal. The free plan is 1,000 credits with only 2 active scenarios, a 15-minute minimum interval, a 5 MB file cap and a 5-minute execution limit. When credits run out, scenarios simply stop until credits are added, and credits expire at the end of the term rather than rolling over. AI modules have dynamic credit usage tied to tokens, file size, pages or run time, and Make Code App costs 2 credits per second of code execution.
Pros
Cons
Make's help centre states that by default one operation equals one credit. Credits are what you buy and consume, while operations are the individual module runs that use them. Most apps charge a fixed rate per module run. Router, Filter and the error handler modules Rollback, Break, Resume, Commit and Ignore consume nothing. Some AI and advanced modules use dynamic amounts tied to tokens, file size, pages or run time.
No. The trigger costs one credit no matter how many items it returns, but each downstream action then runs once per bundle. Make's own example is a trigger that finds five emails costing one credit, followed by an Add a Row action that performs five operations and consumes five credits. Looping over arrays multiplies the cost, so your bill tracks item volume rather than scenario count.
The free plan gives up to one thousand credits a month, two active scenarios, a fifteen-minute minimum interval between scheduled runs, a five-minute maximum execution time, a five-megabyte maximum file size, five hundred twelve megabytes of data transfer and seven-day execution log retention. When credits run out, scenarios stop until more are added. Credits expire at the end of the monthly term and do not carry over.
Make's security page states its infrastructure resides within Amazon AWS EC2 private instances inside an Amazon VPC, with the cluster deployed over two zones for availability, but it names no AWS region there. The help centre documents regional zones for Enterprise, where customers migrate to a dedicated server in their region and allowlist eu1 or us1 hostnames. Default log data retention is thirty days.
Facts sourced from the vendor’s own site, last verified 2026-10-10.
The Weekly Source
One email a week. New listings, repriced tools, and the ones we would skip - including this one if its pricing changes.
