WHAT IS IT?
ToolJet is a self-hosted platform for internal tools. You assemble an interface by dragging components from a catalog, wire it to your databases and APIs, then publish the app to your teams. The repo is the Community Edition under AGPL-3.0: the AI features and the organisation-management side live in a separate commercial offering.
WHY IS IT INTERESTING?
- Visual builder with 60+ components: tables, charts, forms, lists, progress bars. Apps are multi-page and several people can edit one at the same time.
- 80+ data sources: databases, APIs, object storage and SaaS tools connect from the interface, with no hand-written access layer.
- Built-in database: the ToolJet Database acts as no-code storage when you have no backend to connect yet.
- Code where the visual path stops: JavaScript and Python run inside the apps, for the transformations and logic the components do not cover.
- Extensible in-house: the
@tooljet/cliCLI is there to write your own plugins and connectors. - Deployable almost anywhere: Docker, Kubernetes, EC2, ECS, EKS, GKE, Cloud Run, AKS, Azure Container, DigitalOcean, OpenShift and Helm, plus a listing on the AWS and Azure marketplaces.
- Security baseline: AES-256-GCM encryption, proxy-only data flow, SSO, inline comments and granular access control.
- The open-source line is drawn clearly: CE covers the builder, the database, the data sources and self-hosting. App generation from a prompt, the agent builder, RBAC, GitSync, multi-environment, white-labeling and audit logs sit in the paid ToolJet AI tier.
USE CASES
- Stand up a back office on an existing database without hand-writing CRUD.
- Give a support team a screen to read and act on customer data.
- Assemble an operational dashboard that pulls from several APIs and databases.
- Replace a pile of internal scripts with apps that have access control.
- Prototype a business tool before deciding whether it deserves dedicated development.
The repo follows git-flow: develop is the base branch, and stable versions live on main and the v1.x.x tags. For an upgrade, the docs point to the LTS line rather than the latest release.