Zapier vs Self-Hosted n8n: The Real Cost Math

Why the Zapier Bill Keeps Growing

Because Zapier charges you for succeeding.

Every automation platform that bills per task has the same property: the more work your automations do, the more you pay. Automate invoice follow-ups and they run on every invoice. Automate lead capture and it runs on every lead. Your bill scales with your business, which sounds fair until you notice the work being done per task hasn't changed at all.

A workflow that costs $30/month at 2,000 tasks costs $300+/month at 30,000 tasks. Same workflow. Same value per execution. Ten times the price.

What Zapier and Make Cost at Real Volumes

Public pricing, at the volumes a growing 10–30 person business actually hits:

• Zapier: roughly $30/month at 2,000 tasks, around $75/month at 10,000, and into hundreds per month at 50,000+. Multi-step workflows consume tasks per step, not per run: a 6-step workflow triggered 5,000 times is 30,000 tasks.
• Make: cheaper per operation, same shape. Around $10–$35/month at low volumes, climbing steadily. Complex scenarios burn operations fast because every module execution counts.
• Both: key integrations and features (webhooks, multi-step, premium apps) are gated behind higher tiers, so the effective floor is usually a tier above what the calculator suggests.

None of this is dishonest pricing. It's just a rent model, and rent never ends.

What Self-Hosted n8n Costs

n8n's self-hosted community edition is free software. What you pay for is the small server it runs on:

• A $10–$20/month VPS comfortably runs tens of thousands of executions for a typical SMB workload.
• Task count is irrelevant. 500 executions or 500,000, same server bill. Heavy multi-step workflows cost the same as simple ones.
• Nothing is tier-gated. Every node, webhooks, unlimited workflows, unlimited steps, all included, because there are no tiers.

The costs on the other side: someone has to set the server up properly (backups, updates, error alerting), and someone has to fix it when a vendor changes an API. That's either your time or a specialist's. This is the gap a managed setup or an ongoing ops arrangement closes, and it's a fixed cost, not a per-task one.

The Break-Even Point

For most businesses the math flips somewhere around $50–$80/month of Zapier or Make spend:

• Below that, the convenience of hosted tools genuinely wins. Stay put.
• At $75/month you're paying $900/year in rent. A one-time migration to self-hosted n8n plus ~$180/year of hosting typically pays for itself within the first year. Every year after that is nearly pure savings.
• Above $150/month, migration is usually the single highest-ROI automation decision available to you. At that level the build pays for itself inside a quarter.

The compounding effect matters more than the first-year math: businesses that stop paying per task start automating more, because each new workflow is suddenly free to run.

What the Invoice Doesn't Show

Three differences that don't show up on the invoice:

• Your data stays yours. Self-hosted n8n runs on your infrastructure. Customer records, invoices, and messages never transit a third-party automation vendor.
• No vendor veto. Zapier deciding an app is "premium" or Make changing operation counting can't restructure your costs overnight.
• No migration hostage situation. Workflows built on your own server can't be held by a subscription. Cancel everything and they keep running.

Maintenance, Migration, and When to Stay Put

Maintenance is the question everyone asks. Set up properly, with automated backups, health checks, and failure alerts, self-hosted n8n is close to zero-touch. Set up casually, it will eventually bite you at the worst time. The setup quality is the whole game, which is why it's worth doing once, well.

Existing Zapier workflows almost always migrate as-is, and usually improve in the process. Migration is a mapping exercise: triggers, steps, and conditions all have n8n equivalents, and the rebuild is a natural moment to fix the duct tape. See where to start with n8n for what the first workflows typically look like.

Only two or three small workflows? Then stay on Zapier or Make. Sincerely. Self-hosting earns its keep at volume or complexity. An automation audit will tell you which side of the line you're on; the fee comes off any build that follows.

In Short

Per-task pricing is a tax on automation success. If your bill has crossed $50–$80/month and is trending up, the math says migrate: one fixed build cost, a small fixed hosting cost, and workflows that run for free forever after. Book an audit and get the exact numbers for your stack.