Workflow automation comparison

Prefect vs Windmill

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

What the evidence answers

A reading of reviewed official documentation for Prefect and Windmill. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
1 requirement
Documented for one
2 requirements
Not verified for either
4 requirements
Prices
Not like-for-like yet

Price

  • Prefect

    Free plan · paid prices not verified ·

    • Self-hosted: no subscription charge ·
  • Windmill

    Free plan · paid prices not verified ·

    • Community Edition: no subscription charge ·

A complete like-for-like price comparison is not established; the next steps say what is missing.

Common buyer questions answered

Even when labels match, check each source for differences in plans, units and scope.

Hosting responsibility
Prefect Work pools come in three types: Hybrid (a worker in your infrastructure submits runs to your infrastructure), Push (runs are submitted automatically to your configured serverless provider) and Managed (runs are submitted automatically to Prefect-managed infrastructure).Self-hosted: A self-hosted Prefect server stores its data in SQLite by default, with no extra configuration for basic use, and can use PostgreSQL instead.
Windmill Runs on AWS (EKS/ECS), GCP, Azure, Ubicloud, Fly.io, Render.com, Hetzner, Digital Ocean and others; the README’s rule of thumb is one worker per vCPU and 1-2 GB RAMCommunity Edition: Stateless API servers and workers share a PostgreSQL database that holds the job queue and all workspace state

Limits to check

  • Prefect The project describes monitoring through a self-hosted server or managed Prefect Cloud.
  • Prefect Running several self-hosted Prefect servers requires PostgreSQL 14.9 or higher (SQLite does not support multi-server synchronization), Redis for event messaging and a load balancer for API traffic.
  • Windmill The README describes chaining scripts into flows; it does not establish comparable prices or account limits.
  • Windmill Selling, reselling or serving the Community Edition as a managed service, modifying or wrapping it, or re-exposing it to your users as a feature of your product needs a commercial licence

Not verified yet

No reviewed evidence for either product on usage definition, included volume, AI charges and overage charges.

Documented for one product only, shown in the table below: Prefect: trigger polling; Windmill: premium integrations.

Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.

Side-by-side evidence

Documented values with their sources and check dates; requirements the sources do not establish stay marked.

  • Documented as supported
  • Documented as unsupported
  • Not verified Sources do not establish it
  • Not applicable
Documented scope and limits; unverified dimensions remain unknown.
RequirementPrefectWindmill
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

Who it is for
Prefect describes a workflow orchestration framework for Python data pipelines.

Verified Nov 4, 2026 · Prefect: prefect-source

Windmill describes a code-first platform for workflows, apps and AI agents.

Verified Nov 3, 2026 · Windmill: windmill-project

Coverage limits
The project describes monitoring through a self-hosted server or managed Prefect Cloud.

Verified Nov 4, 2026 · Prefect: prefect-source

  • Self-hosted Running several self-hosted Prefect servers requires PostgreSQL 14.9 or higher (SQLite does not support multi-server synchronization), Redis for event messaging and a load balancer for API traffic.
The README describes chaining scripts into flows; it does not establish comparable prices or account limits.

Verified Nov 3, 2026 · Windmill: windmill-project

  • Community Edition Selling, reselling or serving the Community Edition as a managed service, modifying or wrapping it, or re-exposing it to your users as a feature of your product needs a commercial licence
Trigger polling
Deployments can run on Cron, Interval or RRule schedules; the schedules page states no minimum interval.

Publisher documentation in the official PrefectHQ/prefect repository at release 3.9.2 (commit b0479c0c), captured 9 November 2026; supplier description, not a deployment or independent test. Interval schedules accept seconds, ISO 8601 durations or time format strings; no schedule was run.

Verified Nov 10, 2026 · Prefect: prefect-schedules-project

Not verified
Premium integrationsNot verified
The README’s MODE table marks agent mode as (EE), It marks the indexer mode (full-text search) as needing the EE image

Dated publisher project README at release v1.865.0 (commit 2c1edd4c) captured 9 November 2026; supplier description, not a deployment or independent test. Taken from the README’s environment-variable table, where EE is the README’s abbreviation for the Enterprise Edition (its LICENSE_KEY row says Enterprise Edition); other Enterprise-only features are not listed in the README.

Verified Nov 11, 2026 · Windmill: windmill-project

Hosting responsibility
Work pools come in three types: Hybrid (a worker in your infrastructure submits runs to your infrastructure), Push (runs are submitted automatically to your configured serverless provider) and Managed (runs are submitted automatically to Prefect-managed infrastructure).

Publisher documentation in the official PrefectHQ/prefect repository at release 3.9.2 (commit b0479c0c), captured 9 November 2026; supplier description, not a deployment or independent test. The Managed type uses Prefect-managed infrastructure and is listed by the documentation under Prefect Cloud, not under the self-hosted server.

Verified Nov 10, 2026 · Prefect: prefect-workpools-project

  • Self-hosted A self-hosted Prefect server stores its data in SQLite by default, with no extra configuration for basic use, and can use PostgreSQL instead.
Runs on AWS (EKS/ECS), GCP, Azure, Ubicloud, Fly.io, Render.com, Hetzner, Digital Ocean and others; the README’s rule of thumb is one worker per vCPU and 1-2 GB RAM

Dated publisher project README at release v1.865.0 (commit 2c1edd4c) captured 9 November 2026; supplier description, not a deployment or independent test. The README also documents Docker Compose and Kubernetes (Helm) installation. Sizing is a supplier rule of thumb, not a measured requirement.

Verified Nov 11, 2026 · Windmill: windmill-project

  • Community Edition Stateless API servers and workers share a PostgreSQL database that holds the job queue and all workspace state
Coverage note

Project repository README at the captured revision, 4 November 2026. No installation, account, workload, integration or performance test. Exact release, hosted services and third-party terms require separate review.

Publisher project documentation captured 3 November 2026; description of the selected source version, not a hands-on test. Current availability, pricing and terms require confirmation.

4 requirements without reviewed evidence here

Not verified means the reviewed sources do not establish it; it does not mean a product lacks it or that it costs nothing.

  • Usage definition Prefect: not verified · Windmill: not verified
  • Included volume Prefect: not verified · Windmill: not verified
  • AI charges Prefect: not verified · Windmill: not verified
  • Overage charges Prefect: not verified · Windmill: not verified

Next steps

  • Confirm Prefect's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm Windmill's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Ask Prefect about usage definition, included volume and AI charges; our sources do not establish them yet.
  • Ask Windmill about usage definition, included volume and AI charges; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.