Do you need to know how to code to use Make?

No for a simple scenario: connecting two apps is done with clicks, like with Zapier. The canvas gets technical mainly when you add multi-branch routers or handle nested data arrays — at that point, someone comfortable with conditional logic saves time, even without writing code in the strict sense.

What are Make credits, and how do you estimate what a scenario will cost?

The credit replaced the old "operation" as the billing unit. Most modules — read, write, search, transform a piece of data — consume one credit each; modules that call Make's AI can consume several. An ordinary scenario runs at a few credits per execution, but a scenario that loops or retries after an error can climb to several thousand credits in a single run. The four tiers observed on July 30, 2026 — Free, Core at $9/month, Pro at $16/month, Teams at $29/month — all give 10,000 monthly credits; only the features change from tier to tier.

Does my data leave Make's infrastructure?

Yes, systematically: Make offers no self-hosted version. Every scenario runs on the publisher's AWS infrastructure, audited SOC 2 Type II and SOC 3, with an ISO 27001 program for the Enterprise offering. That's serious infrastructure, but third-party infrastructure all the same: for data that must never leave your servers, only n8n and Activepieces fit the bill.

How much does Make cost for a team of ten people?

The bill doesn't depend on the number of user accounts but on the volume of credits consumed by active scenarios. Ten people triggering the same flow therefore don't cost ten times more; it's the number of executions, and their complexity, that sets the bill. The Core tier at $9/month includes 10,000 monthly credits; beyond that, you need to upgrade the tier or reduce scenario frequency.

What's the difference with n8n or Zapier?

Zapier covers the widest app catalog and requires no technical knowledge. n8n is the only one of the three that installs on your own servers. Make sits between the two: a richer canvas than Zapier's for branched scenarios, but with no self-hosting option — the trade-off plays out between visual richness and control over infrastructure.

Make: our review

Make connects your apps on a visual canvas and bills each run in credits rather than in operations. It targets multi-branch scenarios, more elaborate than a simple linear chain.

Free version, then paid·from $9/month

Go to Make's website

What we take away from it

What counts in its favor

The Core tier starts at $9/month for 10,000 monthly credits, a lower entry budget than Zapier for a comparable volume.
The canvas natively handles multi-branch routers and array aggregation on a single screen, where Zapier lines up steps in a column.
The infrastructure has passed a SOC 2 Type II and SOC 3 audit, and the Enterprise offering runs under an ISO 27001-certified security program.

What counts against it

The credit stays as unpredictable as the old operation: a simple module consumes one, a module built on Make's AI can consume several, and a scenario that loops or retries after a failure can go from two to several thousand credits in a single run.
No self-hosted version: unlike n8n or Activepieces, every scenario runs on Make's infrastructure, including the most sensitive data.
The app catalog, around 3,500 connectors, still trails the 9,000+ Zapier advertises.

The right choice for branched scenarios and a tight entry budget, provided you accept that data passes through third-party infrastructure and you watch the credit counter every week.

The facts

First paid tier: $9/month — Core
Data hosting: Hosting not verified
Categories: Automation,No-code
Data verified on: 30 July 2026

What happens to your data

Is your data used to train their models?: Not verified
Subprocessors: Make publishes a DPA and a list of subprocessors referenced from its terms of service; the detail is only accessible by opening that document, not reviewed line by line here.
Retention: Personal data is deleted on request after the subscription ends; the publisher doesn't publish a default retention period on its GDPR page.

Make in detail

Make runs its automations on a canvas where each app appears as a module linked to the others by arrows. The tool targets scenarios where a linear chain no longer suffices: several branches from the same condition, a loop, a router that splits data by a criterion.

The credit replaced the operation, not the price question

Make used to count in "operations". It now counts in credits, a finer unit but just as hard to predict in advance. Most modules — read, search, create, transform a piece of data — consume one credit each; a module built on Make's AI can consume several. The four tiers observed on 30 July 2026 on the pricing page — Free, at no cost, Core at $9/month, Pro at $16/month, Teams at $29/month — all give 10,000 monthly credits: the difference between paid tiers is about features (number of active scenarios, roles, support), not volume.

An ordinary scenario consumes two or three credits per run. A scenario that loops, or that fails and retries automatically, can consume several thousand in a single pass — the pricing page says so itself. The counter shows in the interface, but it needs active watching in the first weeks, like an electricity meter you haven't yet learned to read.

A canvas built for complexity

Here Make goes further than Zapier: the visual canvas natively handles multi-branch routers, repeaters and array aggregation, where Zapier lines up its steps in a single column. A scenario that sorts incoming emails by subject, extracts their attachments and updates three different spreadsheets builds in a single screen, without navigating between separate sub-flows.

What's missing

Two reservations weigh on the choice. The first: Make offers no self-hosted version. Every scenario, including those handling sensitive customer data, runs on the publisher's infrastructure — AWS infrastructure audited SOC 2 Type II and SOC 3, with an ISO 27001 program for the Enterprise offering, but third-party infrastructure all the same. The second: the app catalog, around 3,500 connectors according to the integrations page, still trails the 9,000+ Zapier advertises. Better to check that the everyday business app in use is there before committing to a build.

Who it suits, and who it doesn't

Make wins over teams that need branched scenarios and want a first paid tier under $10 a month, with a richer canvas than Zapier's. It doesn't suit an organization that must keep its data on infrastructure it controls: there, only n8n and Activepieces fit, each with its own billing model to watch closely. Our automation and AI agent work often starts from this initial choice: a rich canvas at an audited third party, or hosting in-house.

Who it's for, and who it isn't

Suited for

SMEs building scenarios with several conditional branches who want to keep them readable in a single canvas
Organizations starting out in automation and looking for a first paid tier under $10 a month

Not a fit

Firms that must keep their data on infrastructure they control: Make offers no self-hosting
Teams that depend on a rare app: Make's catalog, around 3,500 connectors, is narrower than Zapier's

Frequently asked questions

Do you need to know how to code to use Make?: No for a simple scenario: connecting two apps is done with clicks, like with Zapier. The canvas gets technical mainly when you add multi-branch routers or handle nested data arrays — at that point, someone comfortable with conditional logic saves time, even without writing code in the strict sense.
What are Make credits, and how do you estimate what a scenario will cost?: The credit replaced the old "operation" as the billing unit. Most modules — read, write, search, transform a piece of data — consume one credit each; modules that call Make's AI can consume several. An ordinary scenario runs at a few credits per execution, but a scenario that loops or retries after an error can climb to several thousand credits in a single run. The four tiers observed on July 30, 2026 — Free, Core at $9/month, Pro at $16/month, Teams at $29/month — all give 10,000 monthly credits; only the features change from tier to tier.
Does my data leave Make's infrastructure?: Yes, systematically: Make offers no self-hosted version. Every scenario runs on the publisher's AWS infrastructure, audited SOC 2 Type II and SOC 3, with an ISO 27001 program for the Enterprise offering. That's serious infrastructure, but third-party infrastructure all the same: for data that must never leave your servers, only n8n and Activepieces fit the bill.
How much does Make cost for a team of ten people?: The bill doesn't depend on the number of user accounts but on the volume of credits consumed by active scenarios. Ten people triggering the same flow therefore don't cost ten times more; it's the number of executions, and their complexity, that sets the bill. The Core tier at $9/month includes 10,000 monthly credits; beyond that, you need to upgrade the tier or reduce scenario frequency.
What's the difference with n8n or Zapier?: Zapier covers the widest app catalog and requires no technical knowledge. n8n is the only one of the three that installs on your own servers. Make sits between the two: a richer canvas than Zapier's for branched scenarios, but with no self-hosting option — the trade-off plays out between visual richness and control over infrastructure.