Admin panels and dashboards on top of existing data
ToolJet is a platform for building internal tools: admin panels, dashboards and operational screens on top of the databases, APIs and SaaS services a company already runs. Screens are put together by drag and drop, then published for the teams that use them. The GitHub repository calls itself the "open-source foundation of ToolJet AI", the commercial product of ToolJet Solutions Inc., and holds the Community Edition under AGPL-3.0.
In ToolJet the app comes first, and workflows back it up: a button in the app, a webhook or a schedule sets them off. n8n and Activepieces start from the other end: the chain of steps between services.
The comparison of open source workflow automation tools places ToolJet next to workflow engines and AI agent builders.
Over 90 data sources wired in from the UI
- 80+ components: tables, charts, forms, lists. Apps can span several pages and be edited by several people at once.
- 90+ data sources: databases, APIs, object storage and SaaS tools are connected from the UI.
- ToolJet Database: a built-in no-code database for data that has no backend yet.
- JavaScript and Python in queries, to reshape a result or drive a component.
- An MCP server: Claude Code, Codex or Cursor can generate pages, queries and components in a real ToolJet app, which stays editable in the visual builder. Those calls run on the user's own model subscription, not on ToolJet AI credits.
x86 only, with workflows outside the AGPL code
AGPL-3.0, but workflows are not in the open code. The README files workflows, the agent builder, AI app generation, RBAC, GitSync, multi-environment and audit logs under ToolJet AI, the Enterprise edition. That code lives in server/ee and frontend/ee, two Git submodules pointing to repositories the public cannot reach. In the Community Edition, every service in the workflows module throws "Method not implemented.", as the module's AGENTS.md file spells out. The rest falls under AGPL-3.0: anyone running a modified version as a network service has to publish its source.
The docs install the Enterprise edition. The Docker guide pulls tooljet/tooljet:ee-lts-latest, which the system requirements page names as the official Enterprise Edition image, and the README's quick-try command also uses an ee-lts-latest tag. The Community Edition image, tooljet/tooljet-ce, ships under the same version numbers. Without a key, an instance runs on the free Basic license, and an expired trial or subscription drops back to it, losing OpenID SSO and audit logs.
Free self-hosting stops at two builders. The pricing page caps the free self-hosted plan at two people building apps, 50 end users and 10 apps, with SSO limited to Google and GitHub. The workflow builder is included there, while the cloud plans only have it in Enterprise. OIDC, LDAP, SAML, RBAC and GitSync start with the Team plan, at $199 per builder per month.
x86 only, with PostgreSQL 16 and Redis 7. The system requirements page asks for a 64-bit x86 machine (arm64 is not supported) with 4 GB of RAM and 1 vCPU, plus PostgreSQL 16, recommended with at least 8 GB of RAM and 2 vCPUs, and Redis 7, which is required. Redis comes inside the image as long as the server and the worker share one container, and has to run separately once they are split. Workflows only execute on an instance started with WORKER=true, and a run stops after 60 seconds by default. Python inside apps is limited to the standard library.
An LTS line patched several times a week. The 3.20 line opened on September 23, 2025 and had reached v3.20.239-lts by October 5, 2026. Between September 7 and October 7, 2026, 17 LTS releases and 7 betas (the 3.21 line) shipped. The README recommends the LTS for upgrades, and the docs promise a new LTS every three to five months, supported for at least 18 months. The MCP server is still in beta.