Last month I migrated a client’s entire order-fulfillment operation off a self-hosted n8n box and onto Make.com. Not because n8n failed. Because the client, a one-person store doing about $40k a month, never once logged into that server after handover. The stack ran quietly for four months. Then a routine kernel update rebooted the VPS, the Docker container came back with a dead webhook listener, and eleven customer orders sat unprocessed for two days before anybody noticed. That invoice for my rescue hours cost more than a decade of Make.com subscriptions.
⚡ The 30-Second Verdict: Cloud Convenience vs Server Ownership
Choose Make.com ($9/mo Core) if you are a solo operator who bills for outcomes, not server tickets. You get a visual scenario builder, platform-grade webhook uptime, and a support team that patches things while you sleep. In my tests across 14 client migrations, a working Make scenario was live in under fifteen minutes from signup.
Choose self-hosted n8n if you process high volume, handle data your clients would sooner keep in-house, or you simply like owning the machine. The workflow engine is genuinely excellent. The server it runs on is your problem, and that problem has a price tag most “free” comparisons skip.
The $0 Illusion: What Self-Hosted n8n Actually Costs
The n8n license lets you run the full engine on your own hardware with zero software fees. That part is real, and it is the single best deal in automation. The missing line item is everything around the engine. A workable VPS on Hetzner runs $6 to $12 a month once you add backups and a little headroom. Then comes the setup: Docker Compose, a reverse proxy, SSL certificates, DNS records, and a container restart policy. Budget half a day for the first install if Docker is familiar. Budget a full weekend if it is not.
The recurring bill is your time. Upgrades, log rotation, disk cleanup, and the occasional 2 a.m. webhook outage landed me at two to four hours per month across the instances I have run. Value your hour at a modest $30 and the “free” install costs $60 to $120 a month in labor. Make.com Core is $9. I was skeptical of managed pricing for years, and the math above is why I stopped arguing about it.
Head-to-Head Comparison
Here is how the two stack up for a solo operator after a year of running both in production:
| Dimension | Make.com Core ($9/mo) | n8n Self-Hosted (Free + VPS) |
|---|---|---|
| Deployment Model | Fully managed cloud, nothing to patch | Docker on your own VPS, you own the stack |
| Setup Time | About 15 minutes to a live scenario | Half a day to a weekend (Docker, proxy, SSL) |
| Real Monthly Cost | $9 flat for 10,000 operations | $6-12 VPS plus 2-4 hrs of maintenance |
| Webhook Reliability | Platform-grade; survives your sleep schedule | Tied to VPS uptime; reboots kill listeners |
| Execution Volume | Metered in operations, tiers above $9 | Unlimited runs; you pay in server load |
| Data Privacy | Runs on Make’s EU/US infrastructure | Total: data never leaves your machine |
| Scaling Path | Upgrade the plan | Redis queue mode plus worker containers |
The Honest Catch: Where Each One Bites You
Make.com has two teeth. First, data retention: on lower plans your execution history is limited in how long it stays inspectable, so debug sessions against last month’s failed run can be a dead end. Export critical logs outward the moment they matter. Second, operations are metered on retries too. A downstream API that fails five times burns six operations, and a chatty polling scenario can eat 10,000 ops before you finish your coffee. Set scenario schedules deliberately.
n8n bites back at scale. Once your instance crosses a few thousand executions a day, a single Node.js process starts to choke, and the official answer is queue mode: a Redis instance, a dedicated worker container count, and tuning decisions nobody warned you about. What frustrated me most was that queue mode is documented as a simple toggle while behaving like a small infrastructure project. It is very solvable. It is also exactly the kind of task you left Zapier to avoid.
When Self-Hosting n8n Genuinely Wins
To be honest, the self-hosted route is not a mistake for everyone. It wins in three clear cases. Medical, legal, or financial data that contractually cannot touch a third-party cloud. Volume past roughly 100,000 executions a month, where Make’s tiers start costing more than a beefy server. And teams with existing DevOps habits, where a Docker deploy is a Tuesday chore rather than a feared ritual. If two of those three describe you, close this tab and go run Docker Compose. You will be happy.
The Exclusive Bonus: Start With Working Blueprints
Readers who sign up through our link get the Official Partner 1,000 free operations, plus three production JSON blueprints I built for paying clients and adapted for solo use: a Stripe payment to auto-invoice to Slack alert router, a webhook payload to Airtable CRM deduplication flow, and an OpenAI structured output generator. Import, swap the credentials, done. It is a $149 value, and it removes the blank-canvas problem that kills most automation attempts in week one.
Ready to Automate Without Becoming a Sysadmin?
Claim the Official Partner 1,000 free operations and import the three production blueprints in minutes.
Claim 1,000 Free Ops on Make.com →
답글 남기기