At a glance
Make has a free plan and paid tiers priced by credit allowance. At 10,000 credits per month, the pricing page checked on October 14, 2026 showed Core at $9, Pro at $16 and Teams at $29 per month with annual billing. For a small workflow, estimate credits first; upgrade for the specific limits or collaboration features you need.
In this guide
Make subscription prices at 10,000 credits
The official pricing selector displayed these dollar-denominated rates on October 14, 2026. They are an observed quote, not a guarantee for every country; check the checkout currency, taxes and current terms.
| Plan | Pay monthly | Annual-billing monthly equivalent |
|---|---|---|
| Free (1,000 credits/month) | $0 | $0 |
| Core (10,000 credits/month) | $10.47 | $9 |
| Pro (10,000 credits/month) | $18.61 | $16 |
| Teams (10,000 credits/month) | $33.74 | $29 |
| Enterprise | Custom quote | Custom quote |
The annual-billing equivalents above imply $108, $192 and $348 respectively over 12 months, before any checkout adjustments. Annual billing is a commitment rather than a way to pay that lower amount month by month.
A simple credit estimate before choosing a tier
Suppose your workflow handles 400 leads per month and each lead causes three actions charged at one credit each. That hypothetical workflow uses 400 × 3 = 1,200 credits before polling, retries or other activity. It would exceed a 1,000-credit free allowance even though it is only one workflow.
Write down the expected events, chargeable actions per event and background checks separately. Then allow room for peak days. This is a planning calculation, not a measured benchmark: AI modules, code and branching can change the consumption. Use the actual execution record when your workflow runs.
How Make Pricing and Credits Work
Unlike platforms that charge based on individual user seats, Make’s pricing model is anchored in usage. Teams can invite unlimited users to collaborate, build scenarios, and manage connections without incurring per-seat penalties. Cost and plan allocation instead revolve around monthly or annual credit consumption, scenario execution speeds, and administrative capabilities.
Every action taken inside an automation workflow consumes resources from your credit pool. How quickly your credits deplete depends directly on the complexity of your automations, the frequency of execution, and the specific modules in use. Because base subscription rates fluctuate based on the specific credit package selected, buyers should consult Make’s official subscription packages to evaluate current entry costs and custom credit increments.
Credit Allocation and Expiration
Make provides flexibility in how credits are purchased and maintained:
- Monthly billing: Standard monthly subscriptions allocate a fixed quota of credits that reset at the end of each billing cycle. Unused credits generally do not roll over.
- Yearly billing: Check the credit flexibility available on your selected tier. Do not assume that every annual subscription permits the same rollover; credits expire according to the plan’s billing terms.
- Running out of credits: Do not assume workflows keep running automatically. Review extra-credit purchasing options and limits; the current pricing page lists overage protection as an Enterprise feature.
Code Execution and Custom Logic Costs
Standard no-code modules interact directly with third-party APIs or internal data tools. However, when advanced logic is required, Make provides the Make Code App to execute custom JavaScript or Python scripts. Running custom code incurs a distinct consumption rate: 2 credits per 1 second of code execution time. Teams running compute-heavy or long-running scripts must account for this duration-based drain alongside standard step executions.
Data Transfer and Payload Allowances
Data volume is directly tied to your plan level and credit volume:
- Scalable data transfer: Data transfers scale proportionally at 5 GB of data transfer per 10,000 monthly credits on paid tiers, compared to an introductory cap of 512 MB on entry-level free access.
- File size handling: Plans enforce strict per-file size ceilings. Maximum file sizes start at 5 MB on the free tier and scale across tiers to 100 MB, 250 MB, 500 MB, up to 1,000 MB on top-tier enterprise deployments.
Plan Tiers and Execution Boundaries
While credit counts determine raw volume, tier upgrades unlock crucial performance parameters that dictate how quickly and reliably scenarios run.
| Feature / Capability | Free Tier | Standard Paid Tiers | Enterprise Tier |
|---|---|---|---|
| Active Scenarios | 2 active scenarios | Unlimited | Unlimited |
| Minimum Scheduling Interval | 15 minutes | 1 minute | 1 minute |
| Maximum Scenario Execution Time | 5 minutes | 40 minutes | 40 minutes |
| Maximum File Size | 5 MB | 100 MB to 500 MB | 1,000 MB |
| Execution Log Storage | 7 days | 30 days | 60 days |
| Make API Rate Limits | Make API access not included | 60 to 240 calls/minute | 1,000 calls/minute |
| Data Transfer | 512 MB | 5 GB per 10k credits | 5 GB per 10k credits |
Built-in AI and Developer Features
Make includes native artificial intelligence tooling across its platform tiers, enabling workflows that parse unstructured inputs and automate decision-making:
- Maia by Make: Natural conversation interfaces to build and draft automations and AI agents.
- AI ecosystem: Direct integration with over 350 AI applications, alongside a dedicated MCP server to connect external AI frameworks to your Make scenarios.
- Native AI utilities: An AI Content Extractor to pull structured text and metadata from files, an AI Web Search tool (beta) for live web extraction, and Make AI Agents (beta) powered either by Make’s built-in AI provider or your own direct LLM API keys.
- Developer tooling: Beyond custom functions and scenario templates, developers gain access to over 300 public Make API endpoints, custom app builders, and dynamic connections that configure credentials at runtime rather than design time.
Key Limitations to Consider
When planning your automation budget, several operational boundaries should guide your choice:
- Execution timeouts: Scenarios on the free plan are terminated after 5 minutes of run time, while paid plans extend this ceiling to 40 minutes. Long batch processes that exceed 40 minutes must be broken into smaller subscenarios.
- File size ceilings: If your workflows manipulate raw video, audio, or high-resolution graphics, the 100 MB or 250 MB limits on lower-tier plans may block processing, necessitating higher subscription tiers regardless of your overall credit usage.
- Code app compounding: Because running custom JavaScript or Python consumes 2 credits per second, inefficient code loops or network wait times inside scripts can rapidly exhaust monthly credit allowances.
- Log retention caps: Debugging historical errors is limited to 7 days on entry tiers and 30 days on standard paid plans, with 60 days reserved for enterprise tiers.
Who Each Option Suits Best
Freelancers and Solopreneurs
Freelancers handling straightforward, lightweight administrative tasks—such as forwarding lead forms to a CRM or syncing calendar bookings—can often start on the free tier if 2 active scenarios and a 15-minute polling interval suffice. However, anyone requiring near-real-time triggers (1-minute intervals) or running multiple client automations will need to upgrade to a standard paid tier with unlimited active scenarios.
Small Teams and Agencies
Small teams benefit significantly from Make’s non-seat-based pricing. Unlimited users do not mean every tier has the same team permissions. The Teams tier adds team roles; check the controls your agency needs before choosing a lower tier. For businesses handling client documents, invoices, and webhooks, the 100 MB to 250 MB file limits and 40-minute execution windows provide sufficient headroom for multi-step automations.
Scale-ups and High-Volume Organizations
Organizations managing high-throughput data pipelines, internal microservices, or complex ERP connections (such as SAP via on-prem agents) require upper-tier allowances. These environments benefit from priority scenario execution to avoid queuing during peak usage, expanded API rate limits (up to 1,000 calls per minute), and dedicated 60-day audit and execution logs for compliance.
Next Steps
To choose the most cost-effective configuration for your organization:
- Audit your scenario frequency: Determine whether your workflows require 1-minute scheduling or if standard intervals are adequate.
- Calculate payload sizes: Identify the largest files passing through your webhooks to ensure you do not breach the 5 MB, 100 MB, or 250 MB payload ceilings.
- Estimate script runtimes: Check how many seconds your custom JavaScript or Python scripts run, factoring in the 2 credits per second consumption rate.
- Review official package rates: Check the current base pricing and credit volume tiers directly on Make’s pricing page, and consider annual billing if your workflow demand fluctuates across months.
Sources and further reading
Selected Make plan constraints corrected against the official pricing comparison on 29 October 2026. Other sections retain their earlier research date.
Price selector and billing caveats checked 2026-10-14. Other feature sections researched 2026-09-21. Product details can change.