ToolJet vs Depot
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.
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 ToolJet →
See more alternatives to Depot →