We’ve built hundreds of Make scenarios.Today, we recommend n8n. Here’s why.
Scroll used Make for years—on real client projects, complex scenarios, CRM integrations, and business workflows. We know the tool inside out. And it’s precisely this experience that led us to change our default recommendation.
−5 to −10×Sovereignty self-hostedWe’ve connected Make to CRMs, ERPs, invoicing tools, Airtable databases, Stripe webhooks. We’ve handled silent errors at 2 AM, rebuilt scenarios that became unreadable after six months, optimized workflows that were wasting operations. We know what Make does well. We also know where it ends up costing too much.
Three concrete reasons
why we made the change.
Not a trend-driven shift. Three precise, data-backed reasons, born from real projects. Make remains a solid product — it’s our criteria that evolved alongside our clients.
The per-operation bill
Make charges for every action in a scenario. A slightly complex workflow at real scale can multiply the bill by 5 or 10 compared to the initial plan. With self-hosted n8n, it’s a fixed server cost — €50 to €150/month regardless of execution volume. For growing projects, the difference becomes very significant.
Data transiting through US servers
Your credentials, customer data, documents — everything goes through Make’s servers (EU available, but the model remains third-party SaaS). With self-hosted n8n on OVH or Scaleway, data never leaves your infrastructure. For clients with contractual or regulatory requirements, this is often non-negotiable.
Scenarios turning into black boxes
Make is readable for simple flows. Beyond a certain complexity, scenarios become hard to debug, document, and hand over. Self-hosted n8n allows versioning workflows in Git, documenting them, testing them. When a workflow is critical to your operations, it deserves to be treated like code.
You’re on Make —
here’s how we step in.
Staying on Make or moving away — both are valid answers. We intervene in both cases — without turning every mission into a migration project.
Audit and optimization of existing scenarios
Your Make scenarios work, but costs are rising, some fail silently, or no one really knows what they do. We audit, identify scenarios to optimize or remove, and document what needs to be.
Development of new Make scenarios
You need new workflows and you're sticking with Make for now. We build them with clean structure, error handling, logs, and documentation. No disposable scenarios.
Gradual migration to n8n
You’ve identified that Make is too expensive or sovereignty is an issue. We migrate your existing scenarios to self-hosted n8n, workflow by workflow, with zero downtime.
Make vs n8n —
what actually changes.
No bias. Make retains real advantages—number of connectors and immediate ease of use. Everything else leans toward n8n as soon as the project gets serious.
Frequently asked questions
The most common questions we get during scoping. If yours isn’t here, reach out!
You’re using Make. We know the tool—and we can honestly tell you whether it’s worth switching.
Audit, optimization, or migration: we adapt to where you are.
75011 Paris