Windmill vs Zapier

The core difference

Windmill and Zapier automate workflows from opposite starting points. Windmill treats a script as the unit of work: you write a function in TypeScript, Python, Go, or Bash, and Windmill turns it into a runnable step, auto-generates an input form from its parameters, and lets you chain steps into flows. It is closer to a self-hostable developer platform — part job runner, part internal-tools builder — than to a no-code connector.

Zapier treats a pre-built app action as the unit of work. You pick a trigger from one app and an action from another, map fields in a visual editor, and the automation runs in Zapier’s cloud. The entire product optimises for a non-technical operator who wants a new form submission landing in a CRM working in five minutes, without ever seeing code.

That difference decides most comparisons. If your team writes code and wants to own the runtime, Windmill is the more powerful and cheaper platform. If the people building automations do not code and the value is breadth of ready-made integrations, Zapier wins.

Code-first vs no-code

Windmill is code-first by design. Every step can be a full script with dependencies, and the platform handles secrets, scheduling, retries, parallelism, and an auto-generated UI on top. For an engineer, this removes the ceiling no-code tools hit the moment a workflow needs a transform the built-in steps do not support — there is no escape hatch to reach for because code is the default surface.

Zapier is no-code first. It offers Code by Zapier (JavaScript or Python), but it is a paid, secondary step bolted onto an otherwise linear, visual model, not the centre of the product. The field mapper is the cleanest in the category, and for a non-technical user wiring mainstream SaaS together, that polish is exactly the point. The trade is that heavy custom logic, tight loops, or intricate data transforms fight the model in a way they never do on Windmill.

Integrations

Zapier wins the catalog outright. The directory lists roughly 7,000 apps, including obscure, industry-specific, and regional SaaS that no competitor carries, and most mainstream products ship a Zapier integration on day one because it has become the default expectation. If your automation depends on a long-tail tool, Zapier is the safest bet on coverage alone.

Windmill does not compete on a pre-built connector count. Instead, any API is reachable because any step is code: an HTTP call plus a few lines in your language of choice hits any REST endpoint, and Windmill Hub hosts shareable scripts and flows the community has already written. For an engineer this is often faster than hunting for a connector, but for a non-coder it is a wall. The practical read: Zapier for breadth of ready-made actions, Windmill when you would rather write the integration than wait for one.

Pricing

The meters differ sharply. Zapier charges per task, where a task is a single action firing inside a Zap. Triggers are free, but every action step counts separately, so a five-step Zap consumes five tasks per run. The truly free tier is very limited; realistic use starts on the Starter plan around $20 a month, and on multi-step, high-frequency automations the per-task model can balloon into the hundreds per month.

Windmill is open source and self-hostable, so the runtime layer is effectively free — you pay for the infrastructure you run it on. Windmill Cloud and enterprise tiers are priced around compute and workers rather than per task, so the cost does not scale linearly with how many steps a workflow has or how often it fires. For high-volume, multi-step workloads run by a team that can operate a server, Windmill is dramatically cheaper; the cost you take on instead is backups, upgrades, and on-call.

Self-hosting and ownership

This is the cleanest structural split. Windmill ships as an open-source platform with a Docker Compose stack and a Helm chart; the core is AGPL, workers scale horizontally, and Postgres is the backing store. Scripts and flows are plain code that lives in version control and can be synced from a Git repository, so the whole automation layer runs in your own jurisdiction and stays portable. For teams with data-residency, air-gap, or vendor-independence requirements, this is decisive.

Zapier has no self-hosted edition. There is no community release, no on-prem enterprise package, and no public roadmap commitment to add one. Every Zap runs through Zapier’s cloud, which is fine for the majority of workloads and a hard stop for teams that must keep data on their own infrastructure. The upside of the same decision is zero operations: Zapier owns the runtime, secrets, retries, and alerting.

Internal UIs and AI

Windmill doubles as an internal-tools builder. Because every script has typed inputs, Windmill can auto-generate a form or a full app UI on top of a workflow, so a script becomes a button-and-form tool your team can run without touching code. That app-builder layer is something Zapier only partially matches with its separate Interfaces product tier.

On AI, both can call models, but neither is an agent framework. Windmill runs LLM calls as ordinary code steps — wire OpenAI or Anthropic through an HTTP or SDK call and chain it with anything else — which suits developers building custom AI logic. Zapier ships packaged AI Actions and Agents that are fast for "summarise this and post it to Slack" but thinner when the AI step is the workflow itself. The filter is the familiar one: code-heavy AI logic favours Windmill, one-box AI inside a SaaS automation favours Zapier.

Who should choose Windmill

Windmill is the right call for engineering teams who want scripts as workflows, self-hosting, and open-source economics. If your automations are naturally expressed as functions, if you want auto-generated internal tools on top of them, and if predictable compute-based cost beats per-task billing at your volume, Windmill is the more powerful and cheaper platform. Version-controlled scripts, AGPL self-hosting, and portable code make lock-in low. The cost is that you own the deployment and its upkeep, and non-coders cannot build on it unsupervised.

Who should choose Zapier

Zapier is the right call for non-technical teams that need the broadest integration catalog and the gentlest onboarding in the category. Solo founders, marketers, and salespeople wiring CRM, email, and Slack flows get productive in under an hour, and the 7,000-app directory covers long-tail SaaS that Windmill has no pre-built connector for. If nobody on the team wants to write code or operate a server, Zapier handles the runtime, secrets, retries, and alerting, and the premium over a self-hosted tool is worth paying for automations that just work.