n8n has a devoted following in the automation community. It’s genuinely powerful, genuinely flexible, and — in its self-hosted form — genuinely free. It’s also genuinely more complex than the alternatives, with hidden costs that are worth understanding before you commit.
This review covers what n8n actually delivers and who it’s actually for.
What n8n is
n8n is an open-source workflow automation platform with a visual canvas interface. It works similarly to Make and Zapier — you connect nodes on a canvas to build automated workflows between apps. The difference is in what sits underneath:
Open-source: The entire codebase is publicly available, auditable, and modifiable. You’re not locked into a proprietary platform. If n8n the company disappeared tomorrow, the software continues to work.
Self-hostable: You can run n8n on your own server infrastructure — a VPS, AWS, Google Cloud, your own on-premises machine. Data processed by your workflows stays within your environment.
Full code execution: n8n’s Code node allows you to write and execute arbitrary JavaScript or Python. This isn’t a template or a limited expression editor — it’s a full code execution environment within the workflow.
These three characteristics separate n8n from Make and Zapier in ways that matter for specific use cases.
The honest capability assessment
Where n8n is genuinely excellent
Data transformation flexibility: Complex data transformation — reshaping JSON structures, parsing nested arrays, manipulating data formats — is straightforward with n8n’s Code node. In Make, complex transformations require creative use of modules that weren’t designed for it. In n8n, you write the transformation in JavaScript.
Custom logic without workarounds: Anything that requires custom logic — conditional processing that doesn’t fit standard if/then modules, calculations on workflow data, custom error handling — is clean in n8n. You write what you need.
Self-hosted data privacy: For industries with data residency requirements (healthcare, financial services, legal), n8n self-hosted means workflow data never touches a third-party cloud. This is a compliance capability Make and Zapier can’t match.
Cost at high volume: n8n cloud’s execution-based pricing is competitive at high volumes. Self-hosted n8n has no execution limits beyond what your infrastructure handles.
Where n8n has limitations
App integration count: n8n has 400+ integrations versus Make’s 1,400+. For apps not in n8n’s library, you build HTTP request nodes manually — which works but requires knowing the API. In Make, many apps have polished modules with field mapping done for you.
Learning curve: The expression editor (how you reference data from previous nodes) uses JavaScript-like syntax that’s steeper than Make’s point-and-click data mapping. Non-developers find this friction real.
Interface polish: n8n’s canvas is functional but less polished than Make’s. Small things like module icons, error messages, and data preview are more refined in Make.
Managed cloud pricing: n8n.cloud starts at $20/month for 2,500 executions — more expensive than Make Core ($9/month for 10,000 operations). For businesses that want n8n without self-hosting, the cost comparison versus Make doesn’t favor n8n.
The true cost of self-hosted n8n
This is the most important section for small businesses evaluating n8n on cost grounds.
n8n self-hosted is free software. The total cost of ownership includes:
| Cost Component | Monthly Estimate |
|---|---|
| VPS server (Digital Ocean, Hetzner, etc.) | $10-25/month |
| Initial setup (4-8 hours developer time at $75/hr) | $300-600 one-time |
| Monthly maintenance (updates, monitoring, backups, 1-2 hrs) | $75-150/month |
| Total monthly (after setup) | $85-175/month |
| Make Core equivalent | $9/month |
| Make Pro equivalent | $16/month |
For small businesses without an in-house developer who is already being paid regardless of n8n maintenance time, the economics of self-hosted n8n rarely beat Make’s managed cloud service.
The calculus changes when:
- You have a developer on staff whose time is already allocated
- Your compliance requirements mandate self-hosting (the cost is justified by compliance necessity)
- Your automation volume exceeds Make’s tier pricing in a way that makes n8n’s flat infrastructure cost better
Who should use n8n?
Clear yes:
- Businesses with PHIPA, HIPAA, or similar data residency requirements
- Development teams with strong JavaScript skills who want maximum flexibility
- Agencies building automation infrastructure that they want to own fully
- Technical founders who value open-source control and want to avoid vendor lock-in
Clear no:
- Small businesses without developer resources
- Teams that want quick deployment without infrastructure management
- Businesses whose automation needs are well-served by Make’s app library
Worth evaluating:
- Businesses that have hit Make’s pricing ceiling at high automation volume
- Organizations with existing server infrastructure where adding n8n has low marginal cost
n8n cloud vs. n8n self-hosted
If you want n8n without self-hosting complexity, n8n.cloud is the managed version. It removes the infrastructure concern but costs more than Make at comparable usage. For businesses that want n8n specifically (for the code flexibility or open-source control) without self-hosting, n8n.cloud is the right path.
For related comparisons, see our Make vs n8n comparison and our Make.com Review.
Book a free automation audit and we’ll assess your data requirements, technical capacity, and automation scope — then recommend whether n8n self-hosted, n8n cloud, or Make is the right foundation for your workflow automation.