Make vs. n8n vs. Custom Code: Which Automation Should You Build On?

TL;DR

Make for simple glue between SaaS tools, fast. n8n (self-hosted) when data must stay in the EU, volume grows, or logic gets real. Custom code when the workflow is the product, needs testing, or runs at serious scale. Most companies we work with end up with a deliberate mix of the last two.

Every ops team hits this fork: the spreadsheet-and-copy-paste phase is over, and someone has to pick the automation stack. Here's the comparison we walk clients through.

The comparison

	Make	n8n (self-hosted)	Custom code
Setup speed	Minutes	Hours	Days–weeks
Cost at scale	Climbs per operation	Server cost, flat	Development upfront
Data location / GDPR	Their cloud	Your server, EU	Your server
Complexity ceiling	Low–medium	Medium–high	None
Version control & tests	No	Limited	Full
Who maintains it	Anyone	Ops + a developer	Developers

The decision rules

Choose Make when non-developers own the workflow, volume is under ~10,000 operations/month, and no sensitive personal data flows through it. Perfect for marketing glue: form → CRM → Slack.

Choose self-hosted n8n when data residency matters (customer PII stays on your Hetzner box, not a US cloud), when per-operation pricing starts to hurt, or when workflows need branching, retries, and error handling that visual tools can express but Make's pricing punishes. This is the sweet spot for most German SMEs we work with.

Choose custom code when the workflow is business-critical enough to need tests, code review, and version control — or when it is your product. A workflow that bills customers, syncs Salesforce as the system of record, or processes thousands of events an hour doesn't belong in a visual editor that nobody can diff.

The failure mode to avoid

The expensive mistake isn't picking the wrong tool — it's staying on it too long. The 40-node Make scenario that nobody dares touch, with business logic nobody documented, is technical debt with a monthly subscription fee. When a visual workflow needs a comment to be understood, it's time to migrate it.

What we usually deploy

A hybrid: n8n on the client's own EU server for the long tail of internal automations, custom services for the critical paths, and a rule for which is which — "if it touches money or customers' data at scale, it's code."

Untangling an automation sprawl or starting fresh? See our Process Automation services.