ToolJet

Why it's ranked here

ToolJet is a serious, actively engineered platform with a real open core, not a demo. The community edition is AGPL v3 and self-hosts through Docker, Kubernetes, Helm and the major clouds, with a dozen documented deployment targets. The server bootstrap shows production concerns handled in the open: OpenTelemetry tracing, Sentry, graceful shutdown, CSRF origin checks and security headers. The agent angle is the newer reason to look: an MCP server that builds governed apps rather than loose code. The ceiling is the licence split, since AI generation, workflows, audit logs and most access control sit in the paid edition.

What's good

The README lists more than 80 components and more than 90 data source connectors in the free edition, plus a built-in database, multiplayer editing and inline comments. Deployment is well covered, from a single Docker command to Helm and managed container services. The repository ships its own agent guide that maps the editions, the backend and frontend patterns, and a glossary, which makes the codebase easier to extend. Configuration is documented variable by variable, including OpenTelemetry export, Prometheus metrics and a git object cache with explicit size and age limits.

Tradeoffs

Much of what the catalogue highlights is enterprise only: AI app generation, the agent builder, workflows, reusable modules, multiple environments, git sync and row level permissions. That enterprise code lives in private submodules, so the public repository is not the whole product. The one-line Docker quickstart pulls an enterprise image tag, not the community build. Update checks and telemetry to ToolJet's hub are on by default. The sample configuration warns that Python runs without isolation when the sandbox is bypassed on hosts like Fargate or Render. The MCP server is labelled beta.

How to use it well

Pick it when a team needs many internal CRUD screens over existing Postgres, REST or SaaS data and wants to self-host under a copyleft licence. Start with the community edition locally, turn off telemetry if that matters, and pin the LTS image, which the project itself recommends for upgrades. If you plan to use coding agents, point them at the MCP server rather than generating a separate frontend. Budget for the enterprise tier if you need audit logs, SSO provisioning, row level security or scheduled workflows. It is not a general application framework for customer-facing products.

Observed

License

GNU AGPL v3 (community edition)

Backend stack

NestJS with TypeORM on PostgreSQL, Redis for queues

Frontend stack

React with Webpack

Editions

Community, Enterprise and Cloud, selected by an environment variable; EE code in private submodules

Deployment

Docker, Kubernetes, Helm, AWS, GCP, Azure, OpenShift, DigitalOcean, Google Cloud Run

Agent interface

MCP server, labelled beta in the README

In-app scripting

JavaScript and Python

Plugin tooling

ToolJet CLI on npm for creating marketplace plugins

Telemetry

Update checks and telemetry enabled by default, both configurable