Windmill vs Resend
Side-by-side trajectory, velocity, and editorial themes.
Windmill is quietly turning its orchestrator into a DuckLake-native data platform.
Windmill remains a script-and-workflow orchestrator, but its recent output has narrowed almost entirely to the data layer: DuckLake materialization, partitioned assets, freshness, and now schema contracts. The changelog reads less like a general automation tool and more like a managed lakehouse being assembled on top of the existing job engine, with most of the heavier machinery gated to Enterprise Edition.
The direction is a governed, self-maintaining data platform: fork-scoped data environments for isolated iteration, freshness SLAs with an auto-healing watchdog, scheduled compaction and retention, range backfills, and save-time schema validation between producers and consumers. Each release hardens a different operational corner of the DuckLake stack rather than adding breadth, so Windmill is deepening into data-ops rather than widening its surface.
Schema contracts shipped as non-blocking warnings, so the next likely move is to tighten that loop — enforceable contracts or richer lineage on the DuckLake graph. Continued Enterprise gating of the data-ops features (maintenance, freshness watchdog, range backfill) also points to a productized data-platform tier.
Resend goes agent-native with a hosted, OAuth-backed MCP server for email.
Resend is a developer-first email API that has spent the last quarter widening on two fronts. It is building an agent-native surface — an official Claude Code plugin, mentions in AI chats, and now a hosted MCP server — while also creeping past transactional email into audience tooling with CSV contact import, in-email charts, and richer editor previews. The core remains a clean API for sending mail.
The direction is Resend-as-infrastructure that both humans and agents call directly. The MCP thread — a plugin in May, a hosted server in July — turns email into a tool an LLM can invoke over OAuth rather than hand-rolled keys, while the contacts and broadcast work points at competing with marketing-email incumbents, not just transactional senders. Distribution is shifting toward embedding where developers already are, via Vercel's marketplace and Auth0.
Expect the MCP surface to grow from sending into contact and analytics operations, and the audience and broadcast side to keep maturing toward a full marketing-email offering.
See more alternatives to Windmill →
See more alternatives to Resend →