ToolJet shipped 26 release events in 30 days, with 30 GitHub releases over 90 days. That is the headline. The interesting part is not just velocity, it is where the work is going: ToolJet is moving from low-code internal tools toward AI-generated enterprise apps, workflows, and agents.

The official site now frames ToolJet around building full-stack enterprise internal apps from natural language, including AI agents and workflows. The GitHub repository still describes the project as an open-source low-code framework for internal tools, with drag-and-drop UI building, 50+ data sources, self-hosting, app versioning, granular access control, JavaScript and Python execution, and plugin extensibility.

That split is the story. ToolJet is keeping the open-source internal tools foundation alive while repositioning the product around ToolJet AI.

The release feed looks like product hardening, not launch theater

The recent releases are not only AI label changes. v3.20.167-lts added native Gemini AI support. v3.20.164-lts and v3.21.36-beta added AI datasource support for Snowflake. Those are direct signals that ToolJet wants the builder to sit closer to enterprise data and LLM workflows.

But the same release window also includes less flashy work: query autocomplete fixes, module query execution fixes, data query permission fixes, Dynamic Height fixes, Table component sorting, moveable Modal coordinate fixes, and QuickBooks Online marketplace plugin fixes.

That matters. AI app builders fail when the boring editor and runtime details are brittle. ToolJet’s release feed suggests the team knows this. They are shipping AI-facing features while continuing to sand down the parts that app builders hit every day.

The beta stream points in the same direction. v3.21.37-beta includes bulk moving apps across folders with Git sync guards, workspace pull conflict detection, and a fix to prevent Git push from deleting apps when an app name matches a folder name. That is not marketing glitter. That is the kind of version-control plumbing enterprise teams notice when it breaks.

ToolVitals sees a very active open-source project

ToolVitals scores ToolJet at 100 for health, 100 for shipping, and 100 overall, with a 219.1 hot score and 37,956 GitHub stars. The license signal is AGPL-3.0, and the openness classification is OSI-approved OSS, so ToolVitals can call the project open source.

The shipping number is the standout. A lot of internal-tool builders have settled into maintenance mode. ToolJet is not acting like one of them. A 26-release-events-in-30-days pace is aggressive for any developer tool, especially one carrying both an LTS channel and beta work.

What the data does not prove

ToolVitals can see releases, stars, release frequency, SSL, uptime, and public repository signals. It cannot tell whether ToolJet’s AI app builder produces good apps. It cannot measure customer satisfaction, revenue, support quality, security review depth, or how painful upgrades are in a real self-hosted deployment.

The public release notes also do not prove that every AI feature is mature. Native Gemini support and Snowflake AI datasource support are meaningful signals, but they are not the same thing as production reliability across real enterprise workloads.

So the conservative read is this: ToolJet is shipping quickly and aiming hard at AI-assisted internal app development. ToolVitals can support that claim. It cannot certify that the AI experience is better than hand-built low-code apps or custom internal tooling.

How ToolJet compares nearby

LangChain has the same 26 release events in 30 days and a higher hot score at 240.0, with 138,055 GitHub stars. That makes it the larger developer mindshare play, but it is a different bet: LangChain is infrastructure for LLM apps, while ToolJet is a builder for internal business software.

Composio posted 30 release events in 30 days and has 28,557 GitHub stars, compared with ToolJet’s 26 release events and 37,956 stars. Both are moving fast around AI-adjacent developer workflows, but ToolJet’s signal is more tied to app generation, data sources, and enterprise internal tooling.

PostHog is also nearby with 42 release events in 30 days and 34,786 GitHub stars, but ToolVitals classifies it as open core, not OSI-approved OSS. That distinction matters if your team has a hard requirement for an OSI-approved license signal.

Recommendation

If your team builds internal dashboards, admin panels, approval workflows, or database-backed business apps, evaluate ToolJet now because the project is clearly not coasting. Start with the open-source AGPL-3.0 repository, then test the AI builder against one ugly real workflow with permissions, data writes, versioning, and rollback.

Do not judge it from a toy prompt. The release feed says ToolJet is betting on AI-generated internal apps, but the right test is whether it survives the boring enterprise stuff: Git sync, permissions, query behavior, component layout, and data-source edge cases.

Sources