Windmill Self-Hosted
Run scripts and workflows with customer-operated execution workers and an app builder.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Render
- Hetzner
- Fly.io
- Ubicloud
9 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Windmill v1.877.0 configured-AI-key policy hardening
Windmill now rejects direct configured-key calls to provider models outside the administrator-enabled list.
Scope: Workspace or instance AI keys and GitHub App repository resources in self-hosted Windmill.
Workspace members with direct API access could previously spend the configured key on other provider models; direct callers now need JSON with a string model.
Action: Upgrade to v1.877.0 or later, retest API clients and have an administrator resave existing GitHub App repository resources.
Primary source · v1.877.0 release · Repository approval persistence · Reviewed 2026-11-19
What lands where
Supplied by
Vendor or project
Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas
Runs in
Documented customer environment
Customer-operated server, worker processes and PostgreSQL job/state storage
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- DigitalOcean: Boundary not confirmed
- Render: Customer platform workspace
- Hetzner: Customer cloud account
- Fly.io: Customer platform workspace
- Ubicloud: Customer cloud account
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Render
- Hetzner
- Fly.io
- Ubicloud
Servers / containers
Operated by
Your team
Customer operates server/worker containers, PostgreSQL, TLS, job isolation, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- DigitalOcean: Boundary not confirmed · Customer-operated
Provider deployment is documented, but the reviewed evidence does not establish a more specific account or service boundary.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Render: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Hetzner: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Fly.io: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
- Ubicloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Windmill upstream self-hosting provider compatibility ↗ · Source checked 2026-11-12
Windmill production deployment on Ubicloud Kubernetes ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Docker Compose or Kubernetes/Helm with PostgreSQL and worker replicas |
|---|---|
| Infrastructure | Servers / containers Classified servers for the documented long-lived server/worker containers and PostgreSQL queue/state. Fargate compatibility is managed-container hosting, not a function-only software stack. |
| Licensing model | Open Source / Open Core Official repository licensing combines AGPLv3/Apache-2.0 components with proprietary Enterprise feature code. The broad listing includes both community and commercial editions; current plan limits must be checked separately. |
| License | AGPLv3 open-source components; commercial Enterprise licensing and plan-dependent limits |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
The self-hosted OAuth/SSO guide documents user login through Google, Microsoft, GitHub and other configured providers, separately from OAuth resource connections. SAML and SCIM are explicitly Enterprise features; identity-group synchronization and custom claim settings also have edition limits.
Instance user login; built-in SSO and Enterprise SAML have different entitlements · Source ↗ · Enterprise SAML and SCIM ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
v1.877.0 blocks workspace members from spending configured workspace or instance AI keys on models outside the admin-enabled list. Direct configured-key calls now require JSON with a string model; retest clients. Existing GitHub App repository resources require one administrator save before non-admin access.
Windmill configured AI-key proxy and GitHub App repository-resource authorization · Source ↗ · v1.877.0 release ↗ · Repository approval behavior ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The upstream Compose stack includes PostgreSQL and application/worker services. Follow its database-major-version migration notes and choose matching application and dependency releases.
Upstream self-hosted stack; database upgrades require explicit migration planning · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The self-hosting guide suggests roughly one worker per vCPU with 1–2 GB RAM per worker. PostgreSQL, server, proxy and optional editor services require additional capacity; worker concurrency and job isolation change sizing.
Worker rule of thumb, not a complete host minimum or a 100-user/1-TB HA design · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
At v1.878.0, compilable non-enterprise source is AGPLv3, with Apache-licensed clients/specifications. Published Community binaries also contain proprietary features with free internal-use rights and restrictions on redistribution, resale and embedding. Enterprise rights require a commercial licence.
Versioned source and distributed-binary terms differ; cloud infrastructure and support are separate · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
Windmill v1.878.0 was published November 19, 2026. The preceding v1.877.0 release tightened configured AI-key model authorization and changed direct API validation, while also requiring administrators to resave existing GitHub App repository resources before non-admin use.
Upstream Windmill self-hosted release · Source ↗ · Prior reviewed release context ↗ · v1.877.0 policy changes ↗ · AI model allowlist enforcement ↗ · GitHub App repository approvals ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry excludes hosted Windmill Cloud. Review current community limits and Enterprise features rather than assuming all features are included. Workflow code can reach external services; worker sandboxing and credentials need explicit configuration. Official self-hosting documentation gives AWS/Azure/GCP guidance. Windmill v1.877.0 prevents workspace members from bypassing the configured AI-model allowlist through direct proxy or completion API calls. Direct configured-key POSTs must now contain JSON with a string model, and existing GitHub App repository resources remain admin-only until an administrator saves them once. Retest API callers and repository-resource access. v1.878.0 is the reviewed current follow-up release.
Category fit
- Workflow automation
- Code-first scripts, flows, schedules and internal apps with worker execution; enterprise controls and quotas vary.
Compare within Workflow automation
- Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- AWS
- Google Cloud
- Railway
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- Documenso Self-HostedSelf-hosted electronic-signature and document workflow application with a Railway deployment path.
- Railway
- DocuSeal Self-HostedSelf-hosted document forms and electronic-signature workflows with API and webhook integration.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Linode
- Vultr
- Hostinger
- LumaDock
Showing 8 of 25 other listings in Workflow automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow automation →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-host architecture, Docker and provider guidance ↗www.windmill.dev
- Project capabilities and license files ↗github.com
- Self-hosted edition limits ↗www.windmill.dev
- Licensing and edition terms ↗github.com
- Windmill production deployment on Ubicloud Kubernetes ↗www.ubicloud.com
- Windmill v1.878.0 release ↗github.com
- Windmill v1.877.0 policy hardening ↗github.com
- Configured AI-key model enforcement ↗github.com
- GitHub App repository approval persistence ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Windmill upstream self-hosting provider compatibility ↗ · AWS, Azure, Google Cloud, DigitalOcean, Render, Hetzner, Fly.io, Ubicloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream self-hosting section explicitly names AWS EKS/ECS, Google Cloud, Azure, Ubicloud, Fly.io, Render, Hetzner and DigitalOcean, paired with Docker Compose and Helm installation commands. This is an upstream application-hosting compatibility statement; image licensing and enterprise features are separate. Operate the application in a customer cloud account or managed-platform project as appropriate to the selected provider.
- Windmill production deployment on Ubicloud Kubernetes ↗ · Ubicloud
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Ubicloud documents customer account setup, PostgreSQL and Kubernetes provisioning, Windmill Helm deployment, application access and TLS configuration. This is a full customer application deployment, not a PostgreSQL connector or GitHub Actions runner integration.
- Windmill upstream self-hosting provider compatibility ↗ · AWS, Azure, Google Cloud, DigitalOcean, Render, Hetzner, Fly.io, Ubicloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked