Windmill

Open coreWorkflow engine

Code-first orchestration platform for internal software

Homepage Docs Pricing Repository

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $10/mo per seat
Hosted Cloud Free; Team seat-based with execution quota; Enterprise dedicated core + seats + Compute Units. Self-host licensing is recorded under source.self_host, not this ladder.
Free tier: Yes
No card required.
Isolation: Container
shares the host kernel
Regions: —
No actual Cloud regions found; do not infer from office locations.
Capabilities: 23 / 61
12 partial · 26 fail · 0 not assessed
Agent readiness: 9.5/11 · 9/11
read · drive, pre-login surface

Advertised for

Scripts 20+languages · Durable flows · Full code/low code apps · AI agent steps and external MCP tools · Claude Code/Codex/OpenCode sandbox scripts · Windmill AI sessions · Data pipelines (alpha) · Dbt · Scheduled jobs

Built for

Developers, then mixed

· Landing: code-first orchestration platform for internal software.
· Polyglot scripts, CLI/Git deployment, APIs and self-host workers remain central.

01 Pricing Hosted Cloud Free; Team seat-based with execution quota; Enterprise dedicated core + seats + Compute Units. Self-host licensing is recorded under source.self_host, not this ladder.

Tier	EntryFree	Team	TopEnterprise
Price	$0/month	$10/developer/month or $5/operator/monthper seat	from $840/month; default 1 developer + 3 CU = $940/month
Includes	1,000 executions/month; unlimited variables/resources/scripts/apps/flows except abuse; Google/GitHub/GitLab SSO; community support	Per developer seat; operator $5/month, each seat includes one developer or two operators and 10k executions/month; max10 seats; audit retention7days	Published from price $840/month; components core $600/month + developer $40/month (operator $20/month) + standard worker $100/month/CU, 2GB memory. Default simulator 1developer+3CU=$940/month. Dedicated workers/database, unlimited execution, SLA. Do not treat base $840 as included3CU.
Seats	—	1	—

USD per month; Team developer/operator seats; Enterprise core + seats + worker Compute Units·Card required: No·windmill.dev

Overages: Team includes 10k executions per seat/month, maximum 10 seats; no execution-overage price confirmed. Enterprise core $600/month, developers $40/month, operators $20/month, standard workers $100/CU/month; shown standard worker memory limit 2GB. Eight native subworkers count as one CU. No storage/egress rate invented.

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

A restrained blue-and-white technical business site: an illustrated two-column landing hero, spacious rounded pricing cards, and a denser three-column documentation shell.

Corporate
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Containershares the host kernel

Persistence

Volumes are object-storage sync before/after runs, persistent agent memory.20 volumes/workspace and50MB/file CE limit; Enterprise full support.

Snapshots / forks

No evidence of running-compute snapshots/memory snapshots. Workspace/data-table forks are distinct development/database feature.

Resources & limits

Storage

Cloud workspace object storage all plans, Enterprise unlimited; Data Tables managed via instance Postgres; DuckLake; externally connected stores.

Limits & quotas

Hosted Free1000executions/mo; Team10k/seat/mo max10seats; Enterprise dedicated compute. Self-host CE3workspaces50users4groups is separate.

GPU

No advertised first-party Cloud GPU offering.

Access

Deploy interface

dashboardcliapisdkmcpcontainer-imagetemplate

SDK languages

PythonTypeScript/Deno/BunRustGoPowerShell

Network & secrets

Egress controls

Optional nsjail network namespace and operator worker separation; not documented per-job Cloud outbound allowlist.

Secrets

Encrypted Variables & Secrets; job-scoped WM_TOKEN; OIDC workload identity; external secret backends Enterprise.

Bring your own cloud

Self-host available, no separately advertised managed BYOC product.

Placement & use

Jurisdiction

Public hosted compute placement not established; San Francisco/Paris are company locations, not regions.

Advertised workloads

Scripts 20+languagesDurable flowsFull code/low code appsAI agent steps and external MCP toolsClaude Code/Codex/OpenCode sandbox scriptsWindmill AI sessionsData pipelines (alpha)DbtScheduled jobs

04 Capabilities 23 pass · 12 partial · 26 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 2/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Partially supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Partially supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Partially supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Partially supported

Networking & delivery 1/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Partially supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Not supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Partially supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 4/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Partially supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 7/12

Built-in coding agentShips a first-party AI coding agent in the product.

Supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Supported

Data 1/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Partially supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 3/6

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Partially supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Partially supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 5/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

9.5/11

8 full · 3 partial · 86% of applicable checks

llms.txt
Supported
“https://www.windmill.dev/llms.txt — substantive fresh documentation index retained.”
llms-full.txt
Supported
“https://www.windmill.dev/llms-full.txt — 2,841,038-byte comprehensive full text fetched; size-capped POINTER retained.”
robots.txt AI policy
Supported
“https://www.windmill.dev/robots.txt — explicit Allow rules for major AI user agents.”
JSON-LD
Supported
“Homepage JSON-LD includes Organization and SoftwareApplication; retained structural evidence records actual graph.”
Sitemap
Supported
“https://www.windmill.dev/sitemap.xml — nontrivial fresh sitemap retained, linked by robots.”
Meta tags
Supported
“Homepage title, description and OpenGraph inspected in retained structural evidence.”
Markdown negotiation
Partially supported
“Accept: text/markdown on homepage/docs still returns HTML; explicit docs .md variants succeed and are retained.”
Content efficiency
Partially supported
“Homepage 10,459 readable text bytes / 454,488 HTML bytes = 2.301%; retained structural measurement.”
Docs discoverable
Supported
“Homepage header has first-class Docs link; /docs redirects to /docs/intro, both browser and canonical markdown fetched.”
Machine-readable pricing
Supported
“https://www.windmill.dev/pricing — Cloud/Monthly toggle rendered; Free, Team, Enterprise structured prices and comparison retained separately from default self-host view.”
No anti-bot wall
Partially supported
“Default Python urllib User-Agent got homepage 403; Mozilla User-Agent and fresh anonymous desktop browser succeeded. Public surface accessible but headless UA sensitivity prevents blanket full credit.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

9/11

8 full · 2 partial · 82% of applicable checks

Public API
Supported
“https://app.windmill.dev/api/openapi.json — documented REST API, 716 paths.”
OpenAPI spec
Supported
“OpenAPI HTML links /api/openapi.json; fresh valid OpenAPI 3.0.3 fetched, POINTER and structured evidence retained. Root app spec probes are SPA shells, not the spec.”
MCP server
Supported
“https://www.windmill.dev/docs/core_concepts/mcp.md — genuine documented Model Context Protocol endpoints; well-known 404 does not negate this.”
SDK packages
Supported
“Official Python, TypeScript/Deno/Bun, Rust, Go and PowerShell clients; repository and Rust client docs retained.”
Auth documented
Supported
“https://www.windmill.dev/docs/core_concepts/user_tokens.md — bearer authentication and scoped token issuance documented.”
Self-serve credentials
Supported
“OpenAPI documents /auth/login returning a token and /users/tokens/create programmatic scoped token generation; initial account bootstrap still required; issuance not behaviorally tested.”
Webhooks
Partially supported
“https://www.windmill.dev/docs/core_concepts/webhooks.md — extensive bearer-token webhook docs retained, but request signing not established.”
CLI tool
Supported
“https://www.windmill.dev/docs/advanced/local_development — official wmill CLI and sync push deployment.”
Error model
Not supported
“Fresh OpenAPI has no named Error schema or established JSON error contract; error_handling.md documents job/flow errors, not API JSON error model.”
Rate limits documented
Partially supported
“Cloud execution quotas documented on pricing; rate-limit response headers and complete API rate policy not found.”
Agent config files
Supported
“AI sessions document importable SKILL.md skills; local AI development guide provides CLAUDE.md instructions and MCP setup. Missing /agents.md/.well-known/agent is not absence of all configuration.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 4

Claude Code Anthropic
Supported
“run AI coding agents (Claude Code, Codex, OpenCode) in Windmill with sandboxing and persistent file storage; local development optimized for AI (Claude Code, Cursor...).”
Source windmill.dev
Codex CLI OpenAI
Supported
“run AI coding agents (Claude Code, Codex, OpenCode)... build locally with Claude Code or Codex, deploy with `wmill sync push`.”
Source windmill.dev
Cursor Anysphere
Supported
“local development experience optimized for AI (Claude Code, Cursor...); use the MCP to trigger scripts and flows from Claude, Cursor or any MCP client.”
Source windmill.dev
OpenCode opencode
Supported
“run AI coding agents (Claude Code, Codex, OpenCode).”
Source windmill.dev

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 2

SOC 2 Type II
certifiedhostedOfficial support docs explicitly exclude Community Edition; retain Enterprise scope note, do not imply self-host operator certification.
“SOC 2 Type 2 — Compliant; Windmill SOC 2 Type II Attestation 2025”
Source trust.windmill.dev
HIPAA
self-attestedhostedTrust center lists HIPAA compliance and BAA controls; no HIPAA certification implied. Enterprise only according to support docs.
“HIPAA — Compliant”
Source trust.windmill.dev

Regions —

Regions are not disclosed on the public surface.

No actual Cloud regions found; do not infer from office locations.

Legal

Privacy notice Terms of service

08 Open source AGPL-3.0 · fetched by machine, not quoted from marketing

Licence & repository

Licence: AGPL-3.0OSI
Primary language: Rust
Stars: 18,186
Forks: 1,117
Created: 5 May 2022
Archived: No

Activity

Last commit: 14 Oct 2026
Latest release: v1.835.0 · 14 Oct 2026
Issues open / closed: 580 / 1073 · 65% closed

Eight latest releases between 2026-10-08 and 2026-10-14; multiple releases on some days.

Fetched via gh on 15 Oct 2026.

Self-hosting

Methods: dockercomposekuberneteshelm
You operate: postgresobject-storage

Community Edition is free under AGPLv3 plus operator infrastructure/operations: PostgreSQL required; object storage backs volumes and large results. CE limits include 3 workspaces, 50 users, 4 groups, 10 SSO users, 20 volumes/workspace and 50MB/file; workspace object storage quota 10GiB. Enterprise unlocks broader audit/observability, SAML/SCIM, autoscaling and advanced availability. Git sync has limited CE support (up to 2 users), not a blanket Enterprise-only restriction.

Documentation signals 8/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
SupportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

09 Company & presence Facts only, not scored

Company

Headquarters: Not disclosed
Founded: —
Team size: Not disclosed
Hiring: We are hiring; general applications accepted; no named open role on careers page.

Activity

Last release: v1.835.0 2026-10-14T21:25:08Z github.com
Last blog post: Blog first article is How dbt works, and why orchestrators should not split it into tasks; first visible date Aug20,2026 belongs adjacent listing and date of first article not confidently established. Do not invent latest date. windmill.dev

Presence 6

Links found on the public surface scanned; not an exhaustive search.

10 Sources & method How this entry was produced

Public surface only

Everything here was read from windmill.dev's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Workflow engine products →