Zapier vs self-hosted automation

Where self-hosting wins

Volume stops being a pricing event

On Zapier, growth is a bill: 750 tasks is $19.99 a month annually, 2,000 is $49 and 100,000 is $489. Self-hosted, the same growth is a capacity question you answer with hardware you already know how to buy. Windmill makes this explicit even in its commercial form, stating unlimited executions on both paid levels and charging for workers instead, at $120 a month plus $50 per worker.

The licence is a document you can read

Node-RED is Apache-2.0 with nothing attached: no seats, no enterprise directory, no vendor. Activepieces is MIT Expat, with an exclusion that is worth quoting exactly rather than paraphrasing, since its licence file puts "All content that resides under the 'packages/ee/' and 'packages/server/api/src/app/ee' directory" outside the MIT grant. That is a narrower carve-out than most, and it is still a carve-out. Read both files before you plan around either.

The data never leaves

Automations tend to touch the most sensitive systems a company has, since that is the point of them. Self-hosting keeps payloads, credentials and run history inside your own network, which is frequently the only argument that matters in a regulated environment, whatever the arithmetic says.

Where Zapier still wins

Everything you stop paying for, you start providing. A self-hosted automation platform needs a host, upgrades, backups, monitoring and someone who notices when a webhook endpoint stops responding. None of that appears in a licence comparison and all of it appears in a calendar. At Zapier's entry price of $19.99 a month, the break-even against a few hours of engineering time a month is not close.

There is also the catalogue and the audience. Zapier's connector library is the broadest available, and its builder is usable by the operations and marketing people who own most automations in practice. Node-RED in particular is event-driven low-code from the IoT world rather than a business SaaS, so it has no marketplace of pre-built app integrations and no support contract to buy. And Zapier's meter is more generous than it is given credit for: triggers, polling, built-in data tools and failed actions are all free, so a low-volume account with short Zaps genuinely may never feel the limit.

Migrating Zapier to a self-hosted platform

The path most teams take:

1. Inventory first, and be ruthless. List every Zap, its apps and its monthly runs. Most accounts have a handful of automations doing the volume and a long tail doing nothing; only the first group justifies a server.
2. Stand up the platform before you migrate anything. Pick Node-RED, Activepieces or Windmill, run it in production shape with backups and monitoring, and let it sit idle for a week. If that week is annoying, stop here and stay on Zapier.
3. Rebuild the top automations first, and run both for one cycle. Each workflow is recreated by hand and each credential reissued. Keep the Zaps live and reconcile output for a full billing period before cutting over.
4. What does not move. Zap run history and usage records stay with Zapier and disappear with the account. Export what you need for auditing first, and remember that the vendor's uptime record does not transfer either; from cutover, that number is yours.