Tool Reviews
n8n or Make: Should a Small Team Self-Host Its Automation?
The real difference isn't node count — it's who fixes this when it breaks. Judged on data boundaries, failure handling and long-term upkeep.
Most n8n versus Make comparisons stop at node counts and interface screenshots. For a two- or three-person cross-border team, the question that actually decides the outcome is different: when this automation breaks, who fixes it?
The short version: if nobody can reliably own a server and its upgrades, use a managed option (Make, or n8n's own cloud); if you have a genuine data-residency requirement, stable high volume, and someone who can maintain it, then consider self-hosting n8n. The subscription fee you save comes back as ops time.
How they're positioned
| Decision point | n8n | Make |
|---|---|---|
| Deployment | Cloud or self-hosted | Cloud only |
| Community edition | Free community edition available when self-hosting, with most features | No self-hosted form |
| Paid capabilities | SSO, environments, projects, workflow sharing, external storage and Git-based version control sit in paid plans | Capabilities and volume vary by plan |
| Billing model | Varies by plan and deployment | Metered on operations |
| Who it suits | Teams with maintenance capacity or data-location requirements | Teams who want it working today and don't want infrastructure |
n8n's own documentation notes that feature availability changes over time and differs by plan and edition, with the pricing page as the authority. This article deliberately quotes no prices — they move quickly, so check both vendors before committing.
What self-hosting really saves, and really costs
Saves: subscription fees, pressure from per-operation billing, and the ability to keep data inside your own environment.
Costs:
- Deployment and upgrades. Versions, dependencies, database backups, certificate renewals;
- Availability. If the service dies and nobody is alerted, abandoned-cart emails and order notifications stop silently;
- Debugging. You're both the user and the operator when something fails;
- Access and security. Who can edit workflows, where credentials live, whether logs contain customer data.
Convert those into hours per month and compare against the subscription. Most small teams find that unless there's a real compliance requirement, managed wins.
Three questions that decide it
1. Can the data leave your environment?
If workflows touch customer addresses, identity documents, payment data or health-related information, and your obligations restrict where that data sits, self-hosting earns its keep. If the workflow is "post new orders to Slack", standing up a server for it isn't reasonable.
2. Is volume stable and high?
Make meters operations, so dense workflows and frequent polling make cost growth visible. Self-hosting's fixed cost only becomes attractive when monthly operation counts have settled at a high level and the workflows have stopped changing weekly. While you're still editing them daily, iteration speed matters more.
3. Is there a second person who can maintain it?
If only one person understands the system, a holiday is an outage. Before self-hosting, ask: where are the docs, how is a backup restored, who receives the alert. No answers means managed, for now.
A two-week trial
Pick one low-risk but real workflow — "new order → check first-time buyer → write to a sheet → notify the owner":
- build it in both, recording how long the build took;
- deliberately cause three failures (API timeout, missing field, expired auth) and record how long until you noticed and how long until it was fixed;
- have a non-technical colleague try to change one branch condition;
- log a month of actual runs for cost estimation;
- for the self-hosted option, additionally record how long an upgrade takes and whether a backup restore has ever been tested.
Step 2 is the revealing one. Automation is only worth it unattended, and unattended only works if failures reach a human.
Making the call
- No ops capacity, workflows still changing often → managed (Make or n8n cloud);
- Data-residency requirement, stable workflows, a maintainer → self-hosted n8n;
- In between → run managed for three months, then re-evaluate once volume and cost are measurable.
To work out what you should be automating first, see the workflow breakdown in Zapier vs Make for a two-person ecommerce team. For the wider stack, see how to build an AI tool stack for cross-border ecommerce. Tool pages: Make, Zapier.
Sources checked 2026-08-28: n8n deployment options. Plans, capability boundaries and billing models change — check each vendor's current documentation before choosing.