ToolJet vs Windmill
Side-by-side trajectory, velocity, and editorial themes.
ToolJet holds a daily beta/LTS cadence, widening data sources and adding database permissions
ToolJet, an open-source low-code app builder, is shipping almost daily across parallel beta (3.21.x) and LTS (3.20.x) trains. The recent window adds data sources (Databricks, Asana, a DynamoDB overhaul), a new Cascader component, and a permission system for the built-in ToolJet Database, alongside steady AppBuilder and git-sync fixes. It reads as a mature product in broaden-and-harden mode rather than chasing a new direction.
Two threads dominate: expanding integration surface (new connectors plus the native AI/OpenAPI data sources shipped just before this window) and tightening governance (database permissions, role-scoped workspace toggles, git-sync safety). The dual-train model lets riskier features bake in beta before reaching LTS. Expect the permission system and newer connectors to graduate toward LTS while integration breadth keeps growing.
The next releases likely push the ToolJet Database permission system and recent connectors (Databricks, Asana) from beta toward LTS, with continued AppBuilder and query-manager fixes.
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.
See more alternatives to ToolJet →
See more alternatives to Windmill →