* fix: report the real error when a flow's stored version cannot be loaded A flow step that completes on a worker without the flow version cached looked it up, failed (e.g. the flow was deleted, cascading its versions), then fell back to the preview path, whose 'Job isn't a flow job' error replaced the real one. Keep the stored lookup's error when the job has no inline flow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: keep a flow's nodes when it is renamed Renaming a flow moved its versions to the new path but left its flow nodes on the old one, so deleting the old flow row cascaded them away. Runs in flight inside a loop or branch then failed loading their body. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: keep a deleted flow's versions until its runs are done Deleting a flow cascaded its flow_version and flow_node rows away, so runs in flight failed at their next step. The cascade is dropped; the rows are purged when the flow leaves the trash, unless a run of it is still queued, in which case they are kept. Workspace deletion deletes them explicitly, and the version history only lists the current flow's versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: scope moves, reads and the purge to a flow's own versions A deleted flow's versions now survive at its path, so rename, user rename, offboarding, fork cloning, version reads, history and the trash purge only act on the ids the live flow lists. Renames skip nodes already present at the destination with the same content, nodes are no longer purged (they are shared by content and referenced by id), and dependency relocks skip flows that no longer exist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: resolve a flow's latest version among the live flow's own The relock checks and the dependents trigger picked the newest version at the path, which can now be a deleted flow's. Restore the shared query's cache entry under its new text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: set a deleted flow's versions aside instead of scoping every lookup Deleting a flow moves its versions to __deleted/<trash id>; restoring moves them back. Jobs load versions by id so runs in flight keep working, while every lookup by path (history, relocks, versioned runs, renames) stops seeing a deleted flow without special-casing. The purge keeps a set-aside version any queued job references by id, whatever path or kind it was queued under. The per-lookup scoping is reverted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style: rustfmt Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: set versions aside only after an authorized delete, find flow_env by id Row-level security can let a caller read a flow it may not delete; the delete then removes nothing and must not trash it or move its versions. fetch_root_flow_env matched a run's version by path too, so runs of a deleted (or renamed) flow lost their inherited flow_env: match by id for the kinds whose runnable_id is a flow version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: state the authorization contract of the version set-aside helpers Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * perf: read the queue once when purging a deleted flow's versions Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: serialize flow version writes with a concurrent flow delete Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix: make the relock copy wait for a concurrent flow rename Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Open-source, self-hostable code-first platform for workflows, apps and AI agents, running on the fastest self-hostable orchestrator. Engineers write code in 20+ languages and sync it with Git. Business teams build on the same platform with AI, while review, promotion between environments and isolated workers keep engineers in control of what ships. Self-hostable alternative to Lovable, Retool, n8n and a simplified Temporal.
Scripts are turned into sharable UIs, APIs and cron jobs automatically, and can be composed together into flows, data pipelines, AI agents or full-code React and Svelte apps. Supported languages: Python, TypeScript, Go, Bash, SQL, GraphQL, PowerShell, Rust, and more.
Try it - Website - Docs - Discord - Hub - Contributing
Windmill - Code-first platform for workflows, apps and AI agents
Windmill is fully open-sourced (AGPLv3) and Windmill Labs offers dedicated instances and commercial support and licenses.
https://github.com/user-attachments/assets/d80de1d9-64de-4d89-aacd-6df23fa81fc4
- Windmill - Code-first platform for workflows, apps and AI agents
Build with AI, ship with review
Business teams and engineers build on the same Windmill instance. What the AI builds is an ordinary script, flow or app, and goes through the same review as code written by engineers:
- AI sessions build scripts, flows and apps with AI in a workspace fork, with a live preview and a diff to review before deploying.
- Workspace roles decide what each team can author, and folders scope the resources, skills and MCP servers its AI can reach.
- Protection rulesets block direct deployment, so changes reach production only after an engineer reviews and deploys them.
- Dev workspaces keep their own credentials, and promote to prod through Compare & Deploy or a Git pull request.
- Worker groups run AI-built code on its own workers, or on a separate instance.
See let business teams build with AI safely for the full setup. Engineers keep writing code locally with the CLI, the VS Code extension and their coding agent, synced with Git.
Main Concepts
- Define a minimal and generic script in Python, TypeScript, Go or Bash that solves a specific task. The code can be defined in the provided Web IDE or synchronized with your own GitHub repo (e.g. through VS Code extension): provided Web IDE or synchronized with your own GitHub repo (e.g. through VS Code extension):
- Your scripts parameters are automatically parsed and generate a frontend.
- Make it flow! You can chain your scripts or scripts made by the community shared on WindmillHub.
- Build complex UIs on top of your scripts and flows.
Scripts and flows can be triggered by schedules, webhooks, HTTP routes, Kafka, WebSockets, emails, and more.
Build your entire infra on top of Windmill!
What the code looks like
A script is a plain function. Its typed arguments become a generated form, an HTTP endpoint and a CLI command:
import * as wmill from "windmill-client";
import dayjs from "dayjs"; // any npm package, resolved and pinned automatically
export async function main(
customerId: string,
plan: "starter" | "pro", // a union of strings becomes a dropdown
trialDays = 14 // defaults infer the type
) {
const trialEnd = dayjs().add(trialDays, "day").toISOString();
// a data table: the workspace's Postgres, queried without a connection string
const sql = wmill.datatable();
await sql`INSERT INTO trials (customer_id, plan, trial_end) VALUES (${customerId}, ${plan}, ${trialEnd})`.fetch();
// secrets are permissioned by path
const slackToken = await wmill.getVariable("f/sales/slack_token");
await fetch("https://slack.com/api/chat.postMessage", {
method: "POST",
headers: { Authorization: `Bearer ${slackToken}`, "Content-Type": "application/json" },
body: JSON.stringify({ channel: "#sales", text: `New ${plan} trial: ${customerId}` }),
});
console.log(`Trial started for ${customerId}`); // logs stream live in the UI
return { customerId, plan, trialEnd }; // returned as JSON
}
Workflows are code too. Each task runs as its own job with its own logs, and waiting for an approval releases the worker:
import { task, waitForApproval, workflow } from "windmill-client";
async function plan(env: string) {
return { env, changes: 3 };
}
async function apply(plan: { env: string; changes: number }) {
return `applied ${plan.changes} changes to ${plan.env}`;
}
export const main = workflow(async (env: string) => {
const changes = await task(plan)(env);
const approval = await waitForApproval({ timeout: 3600 });
if (!approval.approved) {
return `rejected by ${approval.approver}`;
}
return await task(apply)(changes);
});
Flows can also be built in the visual flow editor or as YAML, with scripts like the first one as steps. See workflows as code.
Data: data tables, DuckDB and DuckLake
- Data tables give each workspace managed Postgres tables, queried with type-checked SQL from TypeScript, Python and DuckDB scripts without exposing a connection string.
- DuckDB scripts query S3 and Azure Blob files (CSV, Parquet, JSON), data tables, Postgres, MySQL and BigQuery in SQL, on your workers.
- DuckLake stores large datasets as lakehouse tables in your workspace object storage, queried in plain SQL.
- Pipelines (alpha) wire scripts by the data they read and write instead of a hand-drawn DAG. This script runs whenever
eventsis materialized, and materializes its own table:
-- pipeline
-- on ducklake://main/events
-- materialize ducklake://main/events_by_kind
ATTACH 'ducklake://main' AS dl;
SELECT kind, count(*) AS n
FROM dl.events
GROUP BY kind;
Existing dbt projects run unmodified as scripts. See the pipelines quickstart.
Develop locally or in the browser
Engineers work from their editor and coding agent, business teams build with AI in the browser, and both land in the same workspace:
| Tool | Description |
|---|---|
| CLI | Sync a workspace with local files and Git, run scripts and flows from the command line. wmill init generates AGENTS.md and skill files for Claude Code, Cursor and other AI tools |
| VS Code extension | Edit and test scripts and flows from VS Code or Cursor with full IDE support |
| Git sync | Two-way sync between a workspace and your Git repository |
| MCP server | Let coding agents and AI clients run scripts, manage resources and monitor jobs in a workspace |
| AI sessions | The same agent loop in the browser, with nothing to install: plan mode, skills and MCP servers, a live preview, and a diff to review before deploying, in a fork of the workspace |
https://github.com/user-attachments/assets/c541c326-e9ae-4602-a09a-1989aaded1e9
You can run scripts locally by passing the right environment variables for the wmill client library to fetch resources and variables from your instance. See local development docs.
Stack
- Database: Postgres (compatible with Aurora, Cloud SQL, Neon, Azure PostgreSQL)
- Backend: Rust - stateless API servers and workers pulling jobs from a Postgres queue
- Frontend: Svelte 5
- Sandboxing: nsjail and PID namespace isolation
- Runtimes:
- TypeScript/JavaScript: Bun (default); Deno only on the
windmill-fullimages - Python: python3 with uv for dependency management
- PHP: only on the
windmill-fullimages - Go, Bash, PowerShell, Rust, C#, Java, Ansible
- TypeScript/JavaScript: Bun (default); Deno only on the
Fastest Self-Hostable Workflow Engine
We have compared Windmill to other self-hostable workflow engines (Airflow, Prefect & Temporal) and Windmill is the most performant solution for both benchmarks: one flow composed of 40 lightweight tasks & one flow composed of 10 long-running tasks.
All methodology & results on our Benchmarks page.
Security
- Sandboxing: nsjail for filesystem/resource isolation, and PID namespace isolation (enabled by default) to prevent jobs from accessing worker process memory
- Secrets: One encryption key per workspace for credentials stored in Windmill's K/V store. We recommend encrypting the Postgres database as well.
See Security documentation for details.
Performance
Once a job started, there is no overhead compared to running the same script on the node with its corresponding runner (Deno/Go/Python/Bash). The added latency from a job being pulled from the queue, started, and then having its result sent back to the database is ~50ms. A typical lightweight deno job will take around 100ms total.
Architecture
Stateless API servers and workers share a PostgreSQL database that holds the job queue and all workspace state (remote agent workers go through the API servers instead). Workers pull jobs by tag, so each worker group can run in its own network, for example dev workers that only reach dev systems and prod workers that only run reviewed code.
How to self-host
For detailed setup options, see Self-Host documentation.
Docker compose
Deploy Windmill with 3 files (docker-compose.yml, Caddyfile, .env):
curl https://raw.githubusercontent.com/windmill-labs/windmill/main/docker-compose.yml -o docker-compose.yml
curl https://raw.githubusercontent.com/windmill-labs/windmill/main/Caddyfile -o Caddyfile
curl https://raw.githubusercontent.com/windmill-labs/windmill/main/.env -o .env
docker compose up -d
Go to http://localhost - default credentials: admin@windmill.dev / changeme
Using an external database: Set DATABASE_URL in .env to point to your managed Postgres (AWS RDS, GCP Cloud SQL, Azure, Neon, etc.) and set db replicas to 0.
Kubernetes (Helm charts)
helm repo add windmill https://windmill-labs.github.io/windmill-helm-charts/
helm install windmill-chart windmill/windmill --namespace=windmill --create-namespace
See windmill-helm-charts for configuration options.
Cloud providers
Windmill works on AWS (EKS/ECS), GCP, Azure, Ubicloud, Fly.io, Render.com, Hetzner, Digital Ocean, and others. Rule of thumb: 1 worker per 1vCPU and 1-2 GB RAM.
OAuth, SSO & SMTP
Configure OAuth and SSO (Google Workspace, Microsoft/Azure, Okta) directly from the superadmin UI. See documentation.
License
- Using the Community Edition as is, internally or through its APIs, is free and needs no commercial license, within the limits and quotas set in the software.
- 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 (iframed public apps excepted) requires a commercial license: contact sales@windmill.dev.
- The binary built from this repository without the
enterprisefeature flag is open source under AGPLv3: the same uses are then allowed under the AGPLv3 terms, or with a commercial license. The API clients and the OpenAPI spec are Apache 2.0.
See LICENSE for the full terms and Pricing for plans.
Integrations
In Windmill, integrations are referred to as resources and resource types. Each Resource has a Resource Type that defines the schema that the resource needs to implement.
On self-hosted instances, you might want to import all the approved resource types from WindmillHub. A setup script will prompt you to have it being synced automatically everyday.
Environment Variables
The variables most deployments set:
| Environment Variable name | Default | Description | Api Server/Worker/All |
|---|---|---|---|
| DATABASE_URL | The Postgres database url. | All | |
| MODE | standalone | The mode of the binary: standalone, server, worker, agent (EE), indexer (EE image, full-text search), mcp | All |
| WORKER_GROUP | default | The worker group the worker belongs to and gets its configuration pulled from | Worker |
| BASE_URL | http://localhost:8000 | The base url that is exposed publicly to access your instance. Is overriden by the instance settings if any. | Server |
| LICENSE_KEY (EE only) | None | License key checked at startup for the Enterprise Edition of Windmill | Worker |
All other variables (database pool, queue, runtimes, private registries, certificates, zombie jobs and more) are documented in the environment variables reference.
Contributing
At this time, we are not seeking outside contribution. Bug reports and feature requests remain very welcome, and small, trivially-verified PRs that fix a problem are still accepted. See CONTRIBUTING.md for the full policy.
To run Windmill from source, see frontend/README_DEV.md.
Copyright
© 2023-2026 Windmill Labs, Inc.






