# Ballet vs Make | when scenarios need reviewable code

> Canonical: https://ballet.dev/vs/make

Make is strong for visual scenario building. When a workflow must be reviewable code across many systems, with approvals and MCP access from Claude or Cursor, Ballet is built for that work.

When scenarios need reviewable code.

Make (formerly Integromat) is a capable visual automation builder. Ballet is for teams that want the same multi-system work written as reviewable, version-controlled code they can run from the web app or from MCP clients like Claude and Cursor.

## Side by side

| | Ballet | Make |
| --- | --- | --- |
| Approach | Plain-English brief → reviewable code | Visual scenario builder |
| New integration | Generated on demand against APIs | Modules and custom HTTP |
| Complex multi-system work | Built for cross-system ops workflows | Scenarios can grow large and hard to audit |
| Output when it matters | Deterministic steps, agentic only where useful | Deterministic modules and routers |
| Review and version control | Generated code, diffs, publish approvals | Scenario versions inside Make |
| MCP / AI clients | Native MCP endpoint for Claude, Cursor, Codex, Hermes | Not an inbound MCP workspace for playbooks |
| Best fit | RevOps, CS Ops and business systems workflows | Visual automation and integration scenarios |

## Past the canvas, into governed workflow code.

### Describe the outcome, keep the code

Ops teams describe weekly reports, lead enrichment, invoice approvals or ticket triage in plain English. Ballet builds the workflow as code your engineers can read before it runs.

### Human gates stay in the path

Approval steps, scoped tool access and replayable runs are part of the playbook, not a separate policy layer you bolt on later.

### Same playbooks from MCP clients

Claude, Cursor, Codex and Hermes can connect to https://api.ballet.dev/mcp and run the same reviewed playbooks your team publishes in Studio.


## Ballet vs Make, answered.

### Should we replace Make entirely?

Not necessarily. Keep Make for visual scenarios that already work. Bring Ballet in for multi-system ops workflows that need reviewable code, publish approvals and MCP access.

### Can Ballet do everything Make does?

Ballet focuses on governed business workflows (RevOps, CS Ops, finance ops) rather than being a general visual iPaaS canvas. Some lightweight Make scenarios are fine to leave where they are.

### How do we start?

Start a Pro trial at app.ballet.dev/signup (14 days, no credit card required), or book a demo if you want Ballet to build the first workflow with you.

### Where can I compare other tools?

See /vs/zapier/, /vs/n8n/ and /vs/workato/ for other comparisons written the same way.

## Next step

We'll turn one painful scenario into a Ballet playbook.

[Start free trial](https://ballet.devhttps://app.ballet.dev/signup)
