Make Free 1,000 credits and two scenarios: when indies should buy Core
Use official Free walls—1,000 credits/month, two active scenarios, 15-minute schedules—to decide when automation needs Core (docs example $9 / 10,000 credits).
When indies wire sheets, mail, and CRM in Make, Free is fine for the first automation. The walls are usually 1,000 credits per month, only two active scenarios, and a 15-minute minimum schedule interval. This page does not compare Make with n8n or Zapier on budget, and it does not re-teach n8n Cloud execution quotas. It freezes Free limits from make.com/en/pricing and the Core pricing example from help.make.com/extra-credits on 2026-10-02. Re-check the pricing slider and your Organization bill before checkout; credit tiers and currency can vary.
Which Free numbers to freeze
The pricing page states there is no time limit on Free and lists 1,000 credits/month, the visual builder, 3000+ apps, routers and filters, customer support, and a 15-minute minimum interval between runs. The comparison table also shows a maximum of two active scenarios, a 15-minute minimum schedule interval, a five-minute max scenario execution time, 512MB data transfer, and seven days of execution log storage. FAQ text explains credits as the billing unit, with most module actions consuming one credit and some AI features more; when Free credits run out, scenarios stop until the next cycle or until you upgrade or buy more.
Free can still prove a serious prototype: two active scenarios, mid/low-frequency polling, routers, and filters all work. Treat it as a sandbox with two production lines and roughly a thousand module actions per month—not a company-wide automation bus. Put 1,000 credits into an automation budget so test runs do not consume the production pool.
Which walls Core mainly removes
Core is described on the pricing page as everything in Free plus unlimited active scenarios, schedules down to the minute, increased data transfer, and Make API access. The official Extra credits help article explains unit math with “if you subscribe to a $9 plan and have 10,000 credits,” so this page treats a common Core entry as the 10,000-credit tier and uses $9 as the documented example price—not as a locked quote for your account. Confirm the live slider and Organization → Subscription at checkout. For solos, the first payment usually buys “a third+ active scenario + shorter schedules + roughly 10× credits,” not a different product.
If you need priority execution, custom variables, or full-text log search, look at Pro; team roles and shared templates belong to Teams. Do not load every advanced capability into the cheapest Core tier. If you only spike occasionally, merge modules and slow polling before buying a much higher credit tier.
Signals that Free should step aside
Upgrade when a third business automation must stay active but the two-scenario wall blocks it; a 15-minute interval makes notifications or sync unacceptable; credits die mid-month and stop scenarios; you need the Make API for external orchestration. You can also upgrade before promising near-real-time sync to customers, so interval and credit headroom are in the SLA notes.
