Windmill vs Buildkite

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.