Install
Try itExperimental
See what an agent can do with Windmill before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s https://app.windmill.dev/api/versionrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflowsevidence →
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Code extensibility — stories about code extensibility in this arenaCode extensibilityevidence →
Stories about code extensibility in this arena
Collaboration governance — stories about collaboration governance in this arenaCollaboration governanceevidence →
Stories about collaboration governance in this arena
Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystemevidence →
Stories about connectors ecosystem in this arena
Deployment embedding — stories about deployment embedding in this arenaDeployment embeddingevidence →
Stories about deployment embedding in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Reliability errors — stories about reliability errors in this arenaReliability errorsevidence →
Stories about reliability errors in this arena
Triggers scheduling — stories about triggers scheduling in this arenaTriggers schedulingevidence →
Stories about triggers scheduling in this arena
Visual builder — stories about visual builder in this arenaVisual builderevidence →
Stories about visual builder in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Windmill stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~5/10
unlocks → Official SDKs · Machine-readable spec · Versioning policy · API sandbox · Install community-built nodes, components, or integrations contributed outside the vendor · Connect to thousands of apps through prebuilt, vendor-maintained integrations · Start from a public library of workflow templates instead of building from scratch
Subscribe to events via webhooks
~5/10
Build against official SDKs
—0/10
Issue scoped/least-privilege API credentials for an agent
~6/10
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—0/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~6/10
unlocks → MCP client
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
✓8/10
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Code extensibility — stories about code extensibility in this arenaCode extensibility
Stories about code extensibility in this arena
Collaboration governance — stories about collaboration governance in this arenaCollaboration governance
Stories about collaboration governance in this arena
Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem
Stories about connectors ecosystem in this arena
Deployment embedding — stories about deployment embedding in this arenaDeployment embedding
Stories about deployment embedding in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Reliability errors — stories about reliability errors in this arenaReliability errors
Stories about reliability errors in this arena
Durability
Error handling
Inspect past execution logs and re-run a failed execution, resuming from the failing step
~3/10
Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling
Stories about triggers scheduling in this arena
Visual builder — stories about visual builder in this arenaVisual builder
Stories about visual builder in this arena
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Cclaimed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Xcommunity | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | 0/10 | ||
Configure automatic retries with backoff for failed steps or activities C Error handling | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 3 | full | 9/10 | Cclaimed | |
Drop into real code (JavaScript or Python) as a step inside a workflow C Code steps | developer | Code extensibility — stories about code extensibility in this arenaCode extensibility | 3 | full | 9/10 | Xcommunity | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | full | 9/10 | Tprobed | |
Add AI agent or LLM steps inside a workflow, with model choice and tool use C Ai steps | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 3 | full | 8/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 8/10 | Xcommunity | |
Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payload G Triggers | developer | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 3 | full | 8/10 | Cclaimed | |
Expose my workflows or connected app actions as MCP tools that an external agent can call C Agent integration | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 3 | full | 8/10 | Tprobed | |
Build multi-step workflows in a visual editor without writing code C Builder | ops user | Visual builder — stories about visual builder in this arenaVisual builder | 3 | partial | 6/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Tprobed | |
Store connection credentials centrally, share them with my team, and control who can use which credential C Credentials | ops user | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 3 | partial | 6/10 | Cclaimed | |
Trigger workflows from events in connected apps (new record, message, email, form submission) C Triggers | ops user | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 3 | partial | 6/10 | Cclaimed | |
Connect to thousands of apps through prebuilt, vendor-maintained integrations C Connectors | ops user | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | full | 9/10 | Cclaimed | |
Build a custom connector or private integration with a documented developer platform, SDK, or CLI G Connector dev | developer | Code extensibility — stories about code extensibility in this arenaCode extensibility | 2 | full | 8/10 | Tprobed | |
Map and transform data between steps with expressions, functions, or formulas C Data mapping | ops user | Code extensibility — stories about code extensibility in this arenaCode extensibility | 2 | full | 8/10 | Cclaimed | |
Run workflows on cron-style schedules with timezone control C Schedules | ops user | Triggers scheduling — stories about triggers scheduling in this arenaTriggers scheduling | 2 | full | 8/10 | Cclaimed | |
Version workflows through source control or environments and promote changes from dev to production C Versioning | developer | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 2 | full | 8/10 | Xcommunity | |
Branch a workflow with conditions, filters, and parallel paths that merge back together C Builder | ops user | Visual builder — stories about visual builder in this arenaVisual builder | 2 | full | 7/10 | Xcommunity | |
Define dedicated error-handling paths or error workflows and get notified when a run fails C Error handling | ops user | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | partial | 7/10 | Xcommunity | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | full | 7/10 | Tprobed | |
Compose reusable sub-workflows or modules that other workflows call C Composition | developer | Visual builder — stories about visual builder in this arenaVisual builder | 2 | partial | 6/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Generate or edit a workflow from a natural-language prompt C Ai authoring | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | partial | 6/10 | Cclaimed | |
Have an agent create, update, and activate a workflow programmatically through the public API C Agent integration | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Cclaimed | |
Run long-lived workflows that wait for days and survive worker or platform restarts without losing state C Durability | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | partial | 5/10 | Cclaimed | |
Run workflows locally or against a dev instance for development and CI testing C Local dev | developer | Deployment embedding — stories about deployment embedding in this arenaDeployment embedding | 2 | partial | 5/10 | Xcommunity | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Xcommunity | |
Inspect past execution logs and re-run a failed execution, resuming from the failing step C Observability | ops user | Reliability errors — stories about reliability errors in this arenaReliability errors | 2 | partial | 3/10 | Cclaimed | |
Pause a workflow to wait for human approval or input before it continues C Human in the loop | ops user | Collaboration governance — stories about collaboration governance in this arenaCollaboration governance | 2 | none | 0/10 | ||
Test a workflow with sample or pinned data and inspect each step's input and output before going live C Testing | developer | Visual builder — stories about visual builder in this arenaVisual builder | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Start from a public library of workflow templates instead of building from scratch C Templates | ops user | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 6/10 | Cclaimed | |
Throttle or queue workflow executions to respect downstream rate limits C Durability | developer | Reliability errors — stories about reliability errors in this arenaReliability errors | 1 | none | 0/10 | ||
Embed the automation platform white-label inside my own product for my customers C Embedding | developer | Deployment embedding — stories about deployment embedding in this arenaDeployment embedding | 1 | none | untested | none yet | |
Install community-built nodes, components, or integrations contributed outside the vendor C Community | developer | Connectors ecosystem — stories about connectors ecosystem in this arenaConnectors ecosystem | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 37 stories with headroom
What would move Windmill’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Windmill's MCP documentation (windmill-docs-17, windmill-probe-4) describes Windmill acting as an MCP *server* so external LLM clients (Claude, Cursor) can call Windmill's scripts/flows — the reverse of the story, which asks whether Windmill can consume/plug into external MCP servers to use their tools.
Connectors ecosystem — stories about connectors ecosystem in this arenaConnect to thousands of apps through prebuilt, vendor-maintained integrations
nonemoves PA Scoreimpact 30
Evidence shows Windmill offers code-based scripts, flows, and triggers (webhooks, Kafka, Postgres, etc.) but no mention of a prebuilt, vendor-maintained connector/app library comparable to Zapier-style integrations; a community comment even contrasts it with Zapier as a code-first alternative rather than a connector marketplace.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI-training data usage or opt-out policies for Windmill; the product is a workflow/automation engine and could plausibly publish a data-usage/privacy policy, but none is documented here.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
The evidence pack documents a CLI (wmill), an MCP server, and workflows-as-code in TypeScript/Python, but none of it describes official client SDKs/libraries for programmatically building against Windmill's API.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack shows an explicit probe for an OpenAPI/Swagger interactive reference that returned 404 on all candidate paths, and no other citation describes an interactive API reference with runnable examples (docs pages are static markdown/CLI/MCP references, not a runnable API explorer).
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Windmill exposes a CLI and API-driven platform, so a downloadable OpenAPI spec is a fair ask, but the evidence pack explicitly shows a probe attempt failing to find any OpenAPI/swagger file at standard paths (all 404s), and no docs page links to a machine-readable spec.
Agenticness — how well agents can access and operate the productRely on versioned APIs with a documented deprecation policy
nonemoves API qualityimpact 30
Windmill exposes webhooks and version-pinned flow endpoints (windmill-docs-16), and a CLI/API surface exists, but there is no evidence of a documented API versioning scheme or deprecation policy; OpenAPI spec probes returned 404s (windmill-probe-3) and no docs mention deprecation practices.
Agenticness — how well agents can access and operate the productDrive the product through a documented public API
partialq5/10moves agent-readyimpact 22.5
Missing: a discoverable OpenAPI/REST API reference page, independent confirmation that third parties integrate via a general public API beyond webhooks/CLI/MCP.
Showing the top 8 of 37 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 40 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs40 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Subscribe to events via webhooks
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Have an agent create, update, and activate a workflow programmatically through the public API
- Expose my workflows or connected app actions as MCP tools that an external agent can call
- Generate or edit a workflow from a natural-language prompt
- Add AI agent or LLM steps inside a workflow, with model choice and tool use
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Drop into real code (JavaScript or Python) as a step inside a workflow
- Build a custom connector or private integration with a documented developer platform, SDK, or CLI
- Map and transform data between steps with expressions, functions, or formulas
- Store connection credentials centrally, share them with my team, and control who can use which credential
- Version workflows through source control or environments and promote changes from dev to production
- Run workflows locally or against a dev instance for development and CI testing
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Run long-lived workflows that wait for days and survive worker or platform restarts without losing state
- Configure automatic retries with backoff for failed steps or activities
- Define dedicated error-handling paths or error workflows and get notified when a run fails
- Inspect past execution logs and re-run a failed execution, resuming from the failing step
- Run workflows on cron-style schedules with timezone control
- Trigger workflows from events in connected apps (new record, message, email, form submission)
- Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payload
- Branch a workflow with conditions, filters, and parallel paths that merge back together
- Build multi-step workflows in a visual editor without writing code
- Compose reusable sub-workflows or modules that other workflows call
Hacker News11 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Drop into real code (JavaScript or Python) as a step inside a workflow
- Version workflows through source control or environments and promote changes from dev to production
- Run workflows locally or against a dev instance for development and CI testing
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Define dedicated error-handling paths or error workflows and get notified when a run fails
- Branch a workflow with conditions, filters, and parallel paths that merge back together
- Build multi-step workflows in a visual editor without writing code
OpenAPI spec4 stories
GitHub README4 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s https://app.windmill.dev/api/versionreproduced$ curl -s https://app.windmill.dev/api/version EE v1.811.0
$npx -y windmill-cli --versionreproduced$ npx -y windmill-cli --version \|/-\|/-\|CLI version: 1.812.0 CLI is up to date Cannot fetch backend version: no active workspace selected, choose one to pick a remote to fetch version of \
$curl -s https://www.windmill.dev/docs/core_concepts/mcp.md | head -6reproduced$ curl -s https://www.windmill.dev/docs/core_concepts/mcp.md | head -6 # Windmill MCP > How do I connect LLMs to Windmill? Use the Model Context Protocol (MCP) to trigger scripts and flows from Claude, Cursor or any MCP client. Windmill supports the [**Model Context Protocol (MCP)**](https://modelcontextprotocol.io/introduction), an open standard that enables seamless interaction between LLMs and tools like Windmill.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
11 of 20 testable claims verified · 0 contradicted → integrity 55/100
23 distinct capability claims found in Windmill’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
11
Verified
9
Unverified
0
Contradicted
20
Undersold
Verified (15)
“Supports writing scripts in TypeScript, Python, Go, PHP, Bash, C#, SQL, Rust, Ruby, R or any Docker image”
Drop into real code (JavaScript or Python) as a step inside a workflowfullproof ↗
“Provides a low-code visual flow builder or YAML for orchestrating functions into flows”
Build multi-step workflows in a visual editor without writing codepartialproof ↗
“Supports UI-based editing plus CLI-driven deployments from a Git repository”
Run workflows locally or against a dev instance for development and CI testingpartialproof ↗
“Supports UI-based editing plus CLI-driven deployments from a Git repository”
“Lets you write orchestration logic as code (TS/Python) with built-in checkpointing, parallelism and fault tolerance”
Drop into real code (JavaScript or Python) as a step inside a workflowfullproof ↗
“Tokens can be scoped to specific resources/actions for least-privilege access”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
“Offers an official CLI (wmill) to interact with Windmill instances from the terminal”
“Can be self-hosted via Docker/Docker Compose or Kubernetes Helm chart for production”
“Deploys push commits to a linked Git repo and can auto-deploy new commits into the workspace”
Version workflows through source control or environments and promote changes from dev to productionfullproof ↗
“Flows support conditional branches, including a 'branch all' mode that runs every branch”
Branch a workflow with conditions, filters, and parallel paths that merge back togetherfullproof ↗
“MCP support lets LLM clients like Claude or Cursor trigger Windmill scripts and flows from chat”
Expose my workflows or connected app actions as MCP tools that an external agent can callfullproof ↗
“MCP support lets LLM clients like Claude or Cursor trigger Windmill scripts and flows from chat”
“Schedules combine a script/flow, arguments, a CRON expression, and optional error/recovery handlers”
Define dedicated error-handling paths or error workflows and get notified when a run failspartialproof ↗
“Runs can be explicitly retagged as failed via a top-level wm_failure field even without a runtime error”
Define dedicated error-handling paths or error workflows and get notified when a run failspartialproof ↗
“App editor is a low-code builder combining drag-and-drop with custom code for building UIs”
Build multi-step workflows in a visual editor without writing codepartialproof ↗
Unverified (10)
“Lets you write orchestration logic as code (TS/Python) with built-in checkpointing, parallelism and fault tolerance”
Run long-lived workflows that wait for days and survive worker or platform restarts without losing statepartialproof ↗
“Steps can be configured to retry automatically with a delay and max attempt count on error”
Configure automatic retries with backoff for failed steps or activitiesfullproof ↗
“Scripts and flows can be triggered via schedules, webhooks, email, HTTP routes, websockets, and many messaging/cloud event sources”
Trigger workflows from events in connected apps (new record, message, email, form submission)partialproof ↗
“Scripts and flows can be triggered via schedules, webhooks, email, HTTP routes, websockets, and many messaging/cloud event sources”
Expose a custom webhook URL that receives external HTTP requests and starts a workflow run with the payloadfullproof ↗
“Scripts and flows can be triggered via schedules, webhooks, email, HTTP routes, websockets, and many messaging/cloud event sources”
Run workflows on cron-style schedules with timezone controlfullproof ↗
“Flows expose version-pinned webhook endpoints targeting a specific numeric flow version”
“Schedules combine a script/flow, arguments, a CRON expression, and optional error/recovery handlers”
Run workflows on cron-style schedules with timezone controlfullproof ↗
“AI Agent steps let you plug various AI providers/models directly into flow execution”
Add AI agent or LLM steps inside a workflow, with model choice and tool usefullproof ↗
“An AI assistant can edit items and open a Compare & Deploy page with those changes preselected for review/deploy”
Generate or edit a workflow from a natural-language promptpartialproof ↗
“Scripts automatically become shareable UIs and can be composed into flows or richer low-code apps”
Compose reusable sub-workflows or modules that other workflows callpartialproof ↗
Undersold (20)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundfullproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Have an agent create, update, and activate a workflow programmatically through the public APIpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventsfullproof ↗
Build a custom connector or private integration with a documented developer platform, SDK, or CLIfullproof ↗
Map and transform data between steps with expressions, functions, or formulasfullproof ↗
Store connection credentials centrally, share them with my team, and control who can use which credentialpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Inspect past execution logs and re-run a failed execution, resuming from the failing steppartialproof ↗
Claims outside our story set (4)
Real capability claims found in Windmill’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Full-code app builder to create custom React/Svelte frontends connected to backend runnables”
source ↗“Encrypts all workspace variables with a symmetric key to prevent leakage”
source ↗“Includes a roles and permissions system to control access within instances and workspaces”
source ↗“Offers 100 free app guests per 30 days who sign in via identity provider without a seat”
source ↗
Business model
AGPLv3 open-source engine you can self-host free; Cloud and Enterprise self-hosted plans priced per seat and per worker with SSO, SAML/SCIM and audit logs.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
