Question 1

What is the logic behind Windmill's pricing?

Accepted Answer

Windmill's pricing is based on compute units (2 worker-gb-month each) and user seats. Operators and external JWT users count as half a seat each. A unique external JWT user is counted per (username/email, scope, instance) tuple. Native workers are an exception and always count as 1 compute unit regardless of memory. Billing uses minute granularity for auto-scaling. This ensures pricing scales linearly with your usage and team size.

Question 2

Which organizations can subscribe to the Pro plan and non-profit EE?

Accepted Answer

The Pro plan is available for individuals, businesses with less than 10 employees and $250k revenues, and seed-stage startups (self-hosted only). Non-profits and universities get 40% off the Enterprise plan.

Question 3

What is an operator? How are external JWT users billed?

Accepted Answer

An operator is a user who can only execute scripts, flows and apps, but not create or edit them. Operators count as half a seat. For external JWT authentication, a unique JWT user is counted per (username/email, scope, instance) tuple used in the last 30 days - so the same email with two different scopes, or on two different instances, counts as two JWT users. Each unique JWT user is billed as half a seat. 1 developer seat or 2 operator/JWT seats count as 1 seat for billing.

Question 4

How are guests billed?

Accepted Answer

A guest is someone with no Windmill account who signs in through the instance SSO/SAML provider (or carries a JWT your own backend signs) and can then open one app and nothing else. This is different from a public app, which anyone holding the URL opens anonymously, with no login and no limit. Guests have no user row and take no seat. The first 100 distinct guest emails over a trailing 30 days are free, including on the free self-hosted Community Edition. Past 100, Enterprise meters guests at 4 guests to 1 seat, rounded up, on cloud as well as self-hosted; a self-hosted instance with no Enterprise license admits no new guest email until the count drops back under 100. Guests are not available on the cloud Free and Team plans. Guests are counted instance-wide by email, so one email is one guest however many workspaces they opened.

Question 5

What is an execution?

Accepted Answer

An execution corresponds to a single job whose duration is less than 1 second. Additional seconds of computation count as additional executions. Flow executions are the sum of each step. Jobs run on one vCPU with 2GB memory, and most take less than 200ms.

Question 6

What are native subworkers?

Accepted Answer

Native subworkers run within a native worker, in the native worker group, pre-configured to listen to native job tags (query languages). They execute under a special mode for increased throughput and go 8 by 8. You can set the number of native subworkers to 0.

Question 7

What are agent workers?

Accepted Answer

Agent workers are remote computing resources that can execute jobs from anywhere. Each agent worker counts as 1 Compute Unit on self-hosted if not used for compute, and 0.5 Compute Unit on cloud if not used for compute.

Question 8

What are compute units?

Accepted Answer

Compute units measure provisioned compute resources based on worker memory limits. 1 compute unit = 2 worker-gb-month. A standard 2GB worker = 1 CU. On self-hosted, any worker with >2GB memory = 2 CU. Native workers are an exception and always count as 1 CU regardless of memory. Minimum billed per worker is 0.5 CU.

Question 9

How many compute units do I need?

Accepted Answer

It depends on your workload. Each worker executes one job at a time and can handle up to 26M jobs/month at 100ms each. Workers come in small (1GB, 0.5 CU), standard (2GB, 1 CU), and large (>2GB, 2 CU) sizes. Native workers are an exception and always count as 1 CU regardless of memory. Use autoscaling for minute-level granularity billing. A free one-month Enterprise trial helps evaluate your needs.

Question 10

How is the use of the number of seats & compute units estimated and reported to Windmill?

Accepted Answer

Compute units are based on worker memory limits in production instances, tracked via lightweight telemetry. Seats are counted as active users (logged in within 30 days) across all instances, with each user counted once. Development/staging instances are not counted for compute units.

Question 11

Do I need a separate license for staging/development environments?

Accepted Answer

No, you can use the same license key for both staging and production. Telemetry only reports production instances for compute units. Seats are counted across all instances but each user is only counted once. Mark non-production instances as non-prod in instance settings.

Question 12

How is payment done?

Accepted Answer

Payment is processed through Stripe and can be made using ACH, bank transfer, Cash App Pay, or credit or debit card. Subscriptions can be made by automatic debit or by invoice.

Question 13

Is Windmill billed based on usage?

Accepted Answer

Only the Teams plan is billed based on actual usage. Enterprise and Pro plans use committed terms for seats and compute units. If usage temporarily exceeds your terms, you get 35 days to address it before your license key expires.

Question 14

Can I increase the subscription terms during the subscription period?

Accepted Answer

Yes, on EE and Pro subscriptions you can increase seats and compute units during the subscription period. A prorated amount is billed for the remaining period. For example, increasing seats 10 months into an annual plan means paying for roughly 2/12 of the annual cost for the additional seats.

Question 15

How can I update my subscription?

Accepted Answer

Enterprise and Pro users can access usage information and invoices through the Windmill Customer Portal. You can also enable or disable automatic renewal and automatic debit (for payment by invoice).

Question 16

What is Windmill's technical support SLA?

Accepted Answer

Windmill provides support with different response times based on issue priorities. The support team is available 24/7, with consistent SLA for both cloud and self-hosted deployments. Enterprise customers also get a dedicated Slack or Discord channel.

Question 17

What is Windmill's security level on cloud?

Accepted Answer

Windmill is SOC 2 Type II compliant, and prioritizes addressing vulnerabilities promptly.

Question 18

Can I get services and workshops from Windmill or partners?

Accepted Answer

Windmill provides priority support to Enterprise customers, including feature requests, bug resolutions, and use case recommendations. For end-to-end implementation and training, Windmill recommends engaging with certified partners.

Question 19

Could the application keep running if Windmill as a company is shut down?

Accepted Answer

Yes, Windmill will continue to operate as long as the license key remains valid, even without an internet connection. If Windmill shuts down, license keys will be extended indefinitely.

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Executions per month	Unlimited	Unlimited
Number of workspaces	3	Unlimited
Maximum number of users	50	Unlimited
Variables, resources, scripts, apps, flows	Unlimited	Unlimited
Groups, folders and granular permissions	Maximum 4 groups	Unlimited
All open source features	Yes	Yes
Public apps (anonymous, no login)	Yes	Yes
Guest app users (identity-provider sign-in, no account)ⓘUnlike a public app, which anyone holding the URL opens with no login at all, a guest signs in through one of the instance's configured identity providers (SSO, or SAML on Enterprise), or carries a JWT your backend signs. A guest has no Windmill account and takes no seat.	100 max / 30 days	100 free, then 4 guests = 1 seat
Oracle DB and MS SQL runtimes as languages (including as dbt adapters)	No	Yes
Multiplayer on WebIDE	No	Yes
Content search	No	Yes
Workspace object storage	10 GiB storage quota	Unlimited
Write-audit-publish for pipeline data tests (failing tests roll back the write)	No	Yes
Range backfill for partitioned pipelines	Single-partition runs only	Yes
Freshness watchdog (auto re-run of stale pipeline assets)	Fresh/stale badge only	Yes
Email triggers	Max 100 emails per day	Unlimited
Postgres triggers	Yes	Yes
WebSocket triggers	Yes	Yes
MQTT triggersⓘSelf-hosted only	Yes	Yes
Kafka triggers	No	Yes
NATS triggers	No	Yes
SQS triggers	No	Yes
GCP triggers	No	Yes
Azure Event Grid triggers	No	Yes
Private Hub	No	Yes
Commercial licence	No	Yes

Free and Open-source

Enterprise

Price

Worker group 1

Agent workers Agent workers are remote computing resources that can execute jobs from anywhere. Each agent worker counts as 1 Compute Unit on self-hosted if not used for compute, and 0.5 Compute Unit on cloud if not used for compute.

Summary

Free and Open-source

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Enterprise

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Frequently asked questions

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Number of users with SSO	10	Uncapped (requires seats)
Workspace secret custom encryption	Yes	Yes
External secret backends (HashiCorp Vault, Azure Key Vault, AWS Secrets Manager)	No	Yes
IAM database authentication for AWS RDS / AuroraⓘSelf-hosted Enterprise only	No	Yes
Entra ID database authentication for Azure PostgreSQL and MS SQLⓘSelf-hosted Enterprise only	No	Yes
Workspace service accounts	No	Yes
Instance-level roles via instance groups	No	Yes
Custom OAuth	No	Yes
SAML & SCIM support including groups synchronization	No	Yes
External auth with JWT (each unique user per email+scope+instance billed as 1/2 seat)	No	Yes
Support level	Community support on Discord	24/7 Priority support with 3h response and dedicated Slack channel
SOC 2 Type II report	No	Yes
Design partners for roadmap	No	Yes

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Audit logs	No	Unlimited
Retention period of jobs runs details	<= 30 days	Unlimited
Schedule error handler	No	Yes
Workspace error handler	No	Yes
Queue metrics	No	Yes
Prometheus metrics	No	Yes
HTTP tracing	No	Yes
OpenTelemetry tracing & logging	No	Yes
Service logs storage on S3	No	Yes
Instance events webhook	No	Yes

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Deployment on Fargate / Docker / KubernetesⓘSelf-hosted only	Yes	Yes
Isolated & dedicated workers and databaseⓘCloud only	No	No
Deploy from GitHub	Yes	Yes
Sync Windmill to a git repository (Git sync)	Up to 2 users	Yes
Agent workers	No	Yes
SSH execution (#ssh directive)	No	Yes
GitHub App	No	Yes
GitLab managed project access token	No	Yes
Deploy to staging/prod web UI	No	Yes
"Run on behalf of" selector when deploying across workspaces	No	Yes
Workspace forksⓘSelf-hosted only — global 3-workspace limit applies on Community Edition	Counts toward 3-workspace limit	Yes
Dev workspaces (persistent fork paired with a lockable prod workspace)ⓘSelf-hosted only — locking the prod workspace reuses protection rulesets (Enterprise)	Counts toward 3-workspace limit	Yes
Infrastructure as code & Kubernetes operatorⓘSelf-hosted only	Yes	Yes
CI test scripts with auto-trigger on deploy	Yes	Yes
OpenID Connect (OIDC)	No	Yes
Codebases & bundles	No	Yes
Private PyPI repositories & npm registries and packages	No	Yes
Workspace dependencies (centralized dependency files)	Yes	Yes
Distributed dependency cache backed by S3	No	Yes
Windows workersⓘSelf-hosted only	No	Yes

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Worker group management UI (incl. Init scripts)ⓘOnly available on self-hosting and enterprise edition on private clusters	No	Yes
AutoscalingⓘSelf-hosted only	No	Yes
Critical alerts	No	Yes
Script-specific workers (dedicated) / High throughput	No	Yes
Concurrency limits	No	Yes

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Priority for stepsⓘSelf-hosted only	No	Yes
Restart deployed flows from any node and version	No	Yes
Lifetime / Delete after use	No	Yes
Approval steps - Adding forms	No	Yes
Approval steps - Adding prompts (self-approval)	No	Yes
Approval steps - Require approvers to be logged in	No	Yes
Approval steps - Disable self-approval	No	Yes
Approval steps - Require approvers to be members of a group	No	Yes
Workflows as code v2 (checkpoint/replay orchestration)	Yes	Yes

Feature	tier-free-selfhost tier	tier-enterprise-selfhost tier
Global CSS	No	Yes
Send schedule reports of Apps (png or pdf) through Slack, Discord or e-mail	No	Yes
Workspace default app	No	Yes
Importing custom React components	No	Yes

Free and Open-source

Enterprise

Price

Worker group 1

Agent workers Agent workers are remote computing resources that can execute jobs from anywhere. Each agent worker counts as 1 Compute Unit on self-hosted if not used for compute, and 0.5 Compute Unit on cloud if not used for compute.

Summary

Feature comparison

Free and Open-source

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Enterprise

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Feature comparison

Platform

Security & Support

Observability

Developers & Deployments

Performance

Flows

Apps

Frequently asked questions