Make review

Make is a hosted visual automation platform: a SaaS layer where teams connect applications, data sources and AI models, then define workflows and AI agents without running an automation server themselves. It sits between the systems in a stack, moving data and triggering actions across them. The homepage lists 3,500+ app integrations and says teams can add custom integrations to anything with an API.

Builders can create workflows by prompting, using drag-and-drop or working from an AI chat through MCP. The platform also offers a visual environment for building, testing, debugging and running automations. JavaScript or Python can be added for custom logic. Make presents observability, governance and agent controls as part of the same platform, so teams can manage workflows and third-party resources in one place. It is suited to connecting services and automating business processes, rather than replacing an application’s database or hosting its core service.

The homepage describes Make as a visual workflow builder with app integrations, custom integrations for anything with an API, and an MCP server for building and running automations from Claude, ChatGPT or Gemini. It also names JavaScript and Python as languages for custom code. That gives developers ways to extend workflows and connect API-backed systems, while keeping the orchestration in Make’s visual environment.

The homepage does not name a Make API style, SDK packages, a CLI, or language-specific client libraries. Confirm SDK support, API authentication and endpoint behavior in Make’s documentation before designing a direct integration. The named integration surface is the visual builder, MCP, built-in app connections and custom integrations to API-backed services. Make says it connects to 3,500+ apps out of the box. Teams building custom integrations should verify supported authentication patterns, payload handling, retries and webhook behavior in the vendor’s docs.

The pricing information lists a free plan at $0 with 1,000 credits per month, two active scenarios, a 15-minute minimum run interval, a five-minute maximum execution time and seven-day execution-log storage. The vendor says the free plan has no time limit and requires no credit card. It is useful for small workflows, but scenario count, scheduling frequency and execution duration constrain production use.

Core is listed at $16 monthly or $12 per month billed annually, with 10,000 credits and the option to scale to 300,000. It allows unlimited active scenarios, a one-minute minimum scheduling interval, 40-minute maximum executions and 30-day logs. Pro is listed at $28 monthly or $21 annually, with 10,000 credits at the base tier and unlimited users. Enterprise pricing is not listed. These figures come from low-confidence pricing information that also shows alternate Core prices of $10.59 and $9, and Pro prices of $18.82 and $16. The listed starting price is $9 per month, but verify it before budgeting. Add-on and overage costs are not published; ask Make how additional credits are billed.

Make is presented as a hosted platform, not as software to install in your own environment. The vendor does not publish a software license or self-hosting option on the vendor's site, so teams requiring an open-source or self-managed deployment should confirm both directly with Make before adopting it.

Data export and migration tooling also need verification. Workflows built around Make’s visual scenarios, app integrations and agent configuration can create switching work if they encode business logic that is not documented elsewhere. Keep critical logic, schemas and credentials documented outside the automation where practical, and ask how scenario definitions and execution data can be exported. Confirm what happens to stored logs and connected data when an account is closed.

The listed plan limits affect scheduling, execution time and log retention: the free tier runs at a minimum 15-minute interval, allows five-minute executions and stores logs for seven days; Core lists one-minute scheduling, 40-minute executions and 30-day logs. Confirm how credits are consumed by each operation, what happens when a scenario reaches its limits, and whether the Enterprise plan changes those constraints. The pricing information does not publish overage costs.

Make says it supports GDPR compliance, SOC 2 Type II and SOC 3, encryption in transit and at rest, SSO, role-based access and audit logs. Before relying on it for critical processes, confirm service-level commitments, incident handling, regional data options and retry behavior with the vendor. Reddit discussion does not offer a clear production assessment of Make: one thread asks for alternatives and commenters discuss other tools, without reporting specific Make reliability issues. Treat that discussion as inconclusive rather than as evidence of uptime or failure.