12 October 20262 min read

Make raises Core, Pro and Teams prices

Make's monthly prices for 10,000 credits have risen. Existing users should check their billing cycle before the next renewal.

Check your Make subscription now

Make's pricing page, retrieved 12 October 2026, now lists higher monthly prices for all three self-service paid plans at 10,000 credits: Core is $12 per month, Pro is $21 and Teams is $38. On 8 October 2026, the same tiers were listed at $9, $16 and $29. If you use Make, open your organisation's billing page now and check the price and renewal date shown for your account before changing or renewing a plan.

  • Record your current plan, credit allowance, billing period and next renewal date.
  • Compare the account quote with the public Make pricing page, retrieved 12 October 2026. The public page currently has monthly payment selected and says annual payment saves 15 percent or more.
  • If the new price applies to your account, check actual credit use before downgrading. A downgrade can stop scenarios that depend on higher-plan features.

What changed

For 10,000 credits per month, the public monthly prices moved from $9 to $12 for Core, from $16 to $21 for Pro, and from $29 to $38 for Teams. That is an increase of $3, $5 and $9 per month respectively. Make explains, retrieved 12 October 2026, that each module action in a scenario counts as one credit. The free tier remains listed at up to 1,000 credits per month.

The billing unit has not changed on the page: Make still charges credits, with one module action such as adding a spreadsheet row or fetching email data counting as one credit. What changed is the public price attached to the paid 10,000-credit tiers.

What the page does not tell us

The public page does not state when the new prices began or whether every existing subscription changes at its next renewal. Account-specific prices, taxes and annual terms may differ. The number that matters for an existing customer is therefore the quote shown inside the account, not an assumption based on the public selector.

This is also not, by itself, a reason to migrate a working automation. A rushed move can cost more than the increase. First measure monthly credit use and identify any features tied to Core, Pro or Teams. Then compare the full workflow, including maintenance and failure handling, rather than only the headline subscription.

A useful comparison needs the same billing period and allowance. Do not compare Make's monthly selector with an annual headline from another provider, and do not equate one credit with one complete workflow run. Count the module actions in the real scenario first; that is the unit Make prices.

← All posts Every claim here links to its source.
Pre-launch

Hourbench builds the workflows these posts talk about.

The Automation Vault is 20 ready-to-run n8n workflows plus a bonus one. It is built and installable, and in final testing against real accounts before it goes on sale.

See what's coming →