Stacks and Flows

Windmill

Turns Python/TypeScript scripts into workflows, UIs, and webhooks — open-source, self-hostable, 13× faster than Airflow.

other open-source Updated 2026-05-09
Visit Windmill →

Pros

  • True developer-grade workflow engine — write Python/TypeScript/Go/Bash, deploy, schedule
  • Self-hostable, AGPLv3 core, generous free Cloud tier
  • Performance is genuinely good — benchmarks show 13× faster than Airflow on common patterns
  • Auto-generates UIs, webhooks, and scheduled jobs from any script
  • Native support for flows (DAGs), apps (UI), and scripts in one platform

Cons

  • No affiliate program; revenue path for content sites is pure SEO traffic only
  • AGPLv3 license has copyleft implications if you embed or redistribute — read carefully
  • Steep learning curve for non-developers; the audience is engineers, full stop
  • Smaller plug-in catalog than n8n/Make; more "write your own" than "click together"
  • Documentation is engineering-first; marketing/ops users will bounce

Best for

  • Engineering teams replacing Airflow, Prefect, or internal cron+Bash systems
  • Backend teams who need workflows + admin UIs + webhooks from the same codebase
  • Self-hosted shops that won't deploy a cloud SaaS and won't tolerate Zapier prices

What it is

Windmill is a self-hostable, open-source platform that turns scripts into runnable, schedulable, observable workflows — and into UIs and webhooks while it’s at it. If n8n is the developer-friendly Zapier, Windmill is the workflow tool for engineers who think n8n still has too much GUI. The core engine is written in Rust, ships as a single binary, and is licensed AGPLv3.

The platform spans three primitives: scripts (any Python/TypeScript/Go/Bash code), flows (DAGs of scripts), and apps (auto-generated UIs that call scripts). Each script becomes a webhook, a CLI command, a scheduled job, and a UI form input — for free, by default.

Who it’s for

Windmill is the right pick when your alternative was Airflow, Prefect, or “we’ll just use cron and Bash”. Backend teams running ETL jobs, data engineering teams orchestrating pipelines, ops teams replacing a sprawl of internal scripts with something observable. It’s the workflow tool of choice for teams whose first reaction to Zapier is “this is a toy.”

It’s a poor fit for non-developers (it’s not for them and isn’t trying to be) and for affiliate-driven content sites (no program — value is pure SEO traffic on developer-intent keywords).

Strengths

  • Genuinely fast. Public benchmarks (windmill.dev/blog) put it 13× faster than Airflow on common DAG patterns. Cold-start latency is in the hundreds of milliseconds, not seconds.
  • Single-binary self-host. Run it on a VPS with Docker, run it on Kubernetes, embed it. The deployment story is engineer-friendly.
  • One platform, three artifacts. Every script becomes a webhook + a schedulable job + a UI. This is closer to what Retool + Airflow + AWS Lambda promise than what they actually deliver together.
  • Real OSS roots. The whole codebase is on GitHub, the contribution graph is alive, the maintainers ship.
  • Code-native. No “drop into code” mode — code is the mode. Pipedream is closest, but Pipedream is cloud-only.

Weaknesses / Watch out

  • AGPLv3 is copyleft. If you self-host Windmill internally for your team’s own work, you’re fine. If you embed it inside a product you ship to customers, you’ll likely owe source disclosure. Talk to a lawyer if in doubt.
  • No affiliate program. From a publisher’s economic standpoint, Windmill pays in SEO traffic, not commissions. That’s a real consideration when stack-recommending.
  • Audience is engineers only. Marketing ops, RevOps, customer success teams should not start here. They will not be productive.
  • Catalog is thin. Pre-built integrations exist but are far fewer than n8n’s 400+ or Make’s 1,800+. The expectation is that you write the API call yourself in 5 lines of TypeScript.
  • Cloud tier exists but isn’t the focus. Windmill Cloud is a real product, but the energy of the project is on self-hosted. Buy accordingly.

Best paired with

  • Postgres + Anthropic Claude — the “self-hosted data agent” stack: scheduled scripts pull data, Claude analyzes it, results land in a Windmill app for review.
  • n8n as a comparison anchor for teams deciding between code-first and low-code — recommending both side by side is fair editorial.
  • Tailscale or Cloudflare Tunnel for exposing self-hosted Windmill safely without standing up a public ingress.

Verdict

Recommended for engineering teams. If you’re a backend engineer who has been muttering “we should just write this in Python” while looking at a $300/month Zapier bill, Windmill is the answer. For everyone else, the wrong tool. No affiliate program means it earns its place purely on editorial merit and SEO long-tail value (Airflow comparisons, Prefect comparisons, self-hosted alternatives) — that’s why we recommend it, but worth being upfront that the publisher economics are different from n8n or Make.

Sources

FAQ

Is Windmill free?
Windmill has a free tier or open-source edition. See pricing details on the official site for paid features and usage limits.
What is Windmill best for?
Engineering teams replacing Airflow, Prefect, or internal cron+Bash systems Backend teams who need workflows + admin UIs + webhooks from the same codebase Self-hosted shops that won't deploy a cloud SaaS and won't tolerate Zapier prices
What are the main downsides of Windmill?
No affiliate program; revenue path for content sites is pure SEO traffic only AGPLv3 license has copyleft implications if you embed or redistribute — read carefully Steep learning curve for non-developers; the audience is engineers, full stop
Who should use Windmill?
Turns Python/TypeScript scripts into workflows, UIs, and webhooks — open-source, self-hostable, 13× faster than Airflow. See our review for the full pros and cons.