Windmill vs Depot
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.
Depot extends from build acceleration into hosted source control with Depot Code.
Depot is broadening from a CI and build-cache company into a full developer-infrastructure platform. This cycle it launched Depot Code — a diskless git server backed by S3 blob storage — into private beta, moved CI and Sandboxes onto a re-architected Depot Metal compute tier, and kept extending Depot CI with new triggers, snapshot improvements, OIDC auth, and Datadog observability.
The direction is a vertically integrated build-and-source stack: Depot Code stores git packfiles as S3 objects and runs stateless git workers, mirroring the same storage-compute separation behind Depot Metal. Each piece plugs into Depot CI, so the company is assembling an end-to-end alternative to the hub-and-spoke GitHub model rather than just accelerating it. The CI surface is maturing in parallel with reliability and integration features.
Expect Depot Code to move toward wider access and tighter Depot CI integration, and GitHub Actions runners and container builds to migrate onto Depot Metal over the coming months as promised.
See more alternatives to Windmill →
See more alternatives to Depot →