Make vs Windmill
Windmill scores higher on the AgentReady, 64/100 against 62/100. They differ on 8 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Make. Make is a visual AI automation platform that enables users to connect any app, data source, or AI model to build and manage automations and AI agents visually, in code, or via natural language prompts.
Windmill. Windmill is a fast, open-source workflow engine and developer platform.
Where Make is ahead
Make passes mcp discoverable, and Windmill does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds adopt: mcp integration available. Windmill misses it.
And on operate, structured, predictable output. Windmill misses it.
Where Windmill is ahead
Windmill passes clear canonical domain and clear product positioning, and Make does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: limits / constraints documented. Make misses it.
And on adopt, agent-compatible signup flow and cli available. Make misses those.
What neither does
Both fail openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, no mandatory sales call, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover. Windmill leads 87 to 80. Make misses clear canonical domain, clear product positioning; Windmill misses mcp discoverable.
Understand. Windmill leads 46 to 38. Make misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Windmill misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented.
Adopt. Windmill leads 67 to 65. Make misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available; Windmill misses no mandatory sales call, programmatic credential creation, mcp integration available.
Operate is whether an agent can run against it in production and recover when a call fails. Make leads 65 to 56. Make misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Windmill misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.
Pricing
Make does not publish a machine-readable starting price and has a free tier. Windmill does not publish one and has a free tier.
Signal by signal
| Signal | Make | Windmill |
|---|---|---|
| AgentReady | 62 | 64 |
| Discovery | 80 | 87 |
| Understanding | 38 | 46 |
| Adoption | 65 | 67 |
| Operability | 65 | 56 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Yes | Yes |
| CLI | Unknown | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Windmill clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Make and Windmill. Alternatives to each: Make, Windmill.
An agent can fetch this as data: POST /v1/compare {"slugs": ["make", "windmill"]}