How to replace Zapier with self-hosted n8n (and when you should not)
Automation tools like Zapier and Make charge per task — every time a workflow runs, you pay. That model is fine until your automations get busy, at which point the bill scales with your success. n8n flips it: you run the automation server yourself and pay for a VPS, not per task.
What n8n is
A visual workflow builder. You drag nodes onto a canvas, connect them, and it runs the flow on a schedule, on a webhook, or on an event. Think "Zapier, but a flowchart you host." It connects to hundreds of services through built-in nodes, reaches anything with an API through an HTTP Request node, and lets you drop into JavaScript or Python when a connector is missing.
Why teams migrate
No task limits. Your ceiling is your server, not your subscription tier.
Data stays yours. Credentials and the data flowing through your workflows never leave your infrastructure.
Real code when you need it. The Code node means you are never blocked by a missing integration.
Self-hosted pricing is flat. One VPS regardless of how many workflows run.
n8n vs Zapier vs Make
| n8n (self-hosted) | Zapier | Make | |
|---|---|---|---|
| Pricing | Flat (your VPS) | Per task | Per operation |
| Data location | Yours | Vendor cloud | Vendor cloud |
| Custom code | Yes (JS/Python) | Limited | Limited |
| Setup effort | You run the server | None | None |
| Licence | Source-available (Sustainable Use) | Proprietary | Proprietary |
Note the licence point: n8n is source-available, not OSI open source. It is free to self-host and use internally, but the licence restricts reselling it as a service. For internal automation that distinction rarely matters — but know it before you build a business on it.
How to migrate
Deploy n8n on a small VPS (2 vCPU / 2–4 GB is plenty), via the official Docker image, with a persistent data volume. Put TLS in front and set an encryption key.
Start with your highest-volume workflow. That is where per-task pricing hurts most, so it is where the move pays off fastest.
Rebuild, do not expect a perfect import. Zapier/Make exports rarely map one-to-one; the logic is usually simpler to recreate on the n8n canvas.
Test the error path. Add an error branch and a retry, not just the happy path.
Back up the n8n data volume — it holds your workflow definitions and credentials.
When NOT to migrate
If you run a handful of light automations a month, the per-task tools cost little and save you all the maintenance. Stay.
If you are not comfortable running a server (updates, backups, TLS), a hosted tool may genuinely be cheaper than your time.
If a workflow is business-critical, weigh the reliability of a supported SaaS against your own uptime discipline.
For the right use case — heavy, internal, credential-holding automation — self-hosted n8n is a clear win. Specs and steps: /app-hosting/n8n, and what n8n is.