Answer in brief: ToolJet is an actively maintained open-source low-code platform for internal tools, dashboards, workflows, and AI agents, and the latest stable release at the 2026-08-16 snapshot is v3.20.212-lts. It is worth piloting if your required data sources are covered, you can operate and upgrade a self-hosted Docker or Kubernetes stack, and AGPL-3.0 fits your business. Production readiness is not automatic: enterprise features such as GitSync, audit logs, and embedded apps sit in the commercial ToolJet AI tier, and niche connectors may need custom plugins. This article is a source and documentation review, not a local install or benchmark test.

What the August 2026 releases changed

ToolJet runs two release lines: an LTS line aimed at production and a beta line for newer work. At the 2026-08-16 snapshot, the newest stable tag is v3.20.212-lts and the newest prerelease is v3.21.60-beta. According to the maintainers’ release notes, recent LTS work is mostly component and reliability improvement rather than a platform rewrite:

• v3.20.212-lts adds dynamic number format support to Currency Input, dynamic height to Timeline, Filepicker, Reorderable List, RadioButtonV2, and Tags, plus a camera flip option in the Camera widget.
• The same release moves table row-click event execution to a macrotask so exposed variables resolve before events fire, fixes button column resizing so column width persists, and updates Redis installation to the official repository for version 7.x across Dockerfiles.
• v3.20.211-lts adds global certificates across data source connections and automated RDS SSL certificate setup, and fixes values typed into a new table row being lost when tabbing between fields.
• v3.20.210-lts is described by the maintainers as patching all Critical/High CVEs found in a container scan, covering OS and app dependencies.
• In the beta line, v3.21.60-beta cherry-picks a fix for stale exposed values in table row-click events, and v3.21.59-beta guards against null group and app names in the Groups permissions UI.

Interpretation, with conditions: the release cadence is a positive maintenance signal, but it also means self-hosting is an ongoing commitment. If you deploy LTS, plan to review each new tag; if you deploy beta, expect change and occasional fixes like the row-click event patch landing in later LTS releases too.

Who should consider ToolJet

Per the repository README, ToolJet describes itself as the open-source foundation of ToolJet AI and provides a visual app builder with 60+ components, a built-in ToolJet Database, 80+ data sources, multiplayer editing, inline comments and access control, plugin extensibility through the ToolJet CLI, and the ability to run JavaScript and Python inside apps. The Community Edition is the self-hostable part; AI app generation, AI query building, AI debugging, and an agent builder are listed under the ToolJet AI enterprise tier.

ToolJet is a reasonable candidate if you already have databases or APIs and need admin consoles, dashboards, approval flows, or operational screens without a separate full-stack project per screen. If you do not want to run infrastructure, the README points to ToolJet Cloud and AWS/Azure Marketplace listings. It is a weaker fit if you need enterprise controls in the free tier, if your critical connector is missing, or if no one on your team owns upgrades, backups, and patching.

What to check before production

Deployment and operations

The README’s quickstart runs Docker with the tooljet/try:ee-lts-latest image, mounts a volume for PostgreSQL 13 data, and binds port 80. The command also pins –platform linux/amd64, so verify ARM64 image support before committing to Apple Silicon or ARM servers. Supported paths listed in the README include Docker, Kubernetes/Helm, AWS EC2, ECS, and EKS, GCP GKE and Cloud Run, Azure AKS and Azure Container, OpenShift, and DigitalOcean. The stack is not a single container: PostgreSQL and Redis are part of the picture, so backups, credentials, upgrades, and dependency patching are operational work you inherit.

Upgrade path and tag choice

The README advises using the LTS version over the latest version for upgrades, citing production bug fixes, security patches, and performance enhancements. LTS tags in this snapshot arrived on 2026-08-11, 08-12, and 08-14, which is frequent for a production line. One documentation inconsistency to note: the README says stable code lives on main or tags labeled v1.x.x, while current releases are v3.x tags. That is minor, but confirm the actual tag and branch you plan to deploy rather than trusting the README text.

License and security posture

ToolJet is AGPL-3.0, attributed to ToolJet Solutions Inc. in the README. Internal use is usually manageable, but network distribution of modified versions triggers obligations, so run it past counsel if you plan to offer ToolJet-based tools to other organizations. The README’s security claims, including AES-256-GCM encryption, proxy-only data flow, and SSO support, are maintainer claims; verify them in your own deployment. The recent LTS notes do show security work: the 2026-08-11 release says critical and high CVEs from a container scan were patched, but that is a report from the maintainers, not an independent audit.

Limitations and where custom development appears

The repository had 1,128 open issues at the 2026-08-16 snapshot. That count includes long-running feature requests: Amazon DocumentDB support has been requested since December 2023 and remains open, and community template issues such as a gym membership management system and a Unix time converter are still open. This is not evidence of a broken project; it is evidence that not every connector or community template will arrive on your schedule. If your stack includes less common systems, plan for plugin development with the ToolJet CLI or budget for integration work.

The Community Edition versus enterprise split is the bigger constraint. Multi-environment management, GitSync and CI/CD, audit logs, advanced RBAC with custom groups, row/component/page/query-level permissions, white-labeling, embedded apps, and SLAs are all listed under ToolJet AI, not Community Edition. If those matter, they are a commercial decision or custom work, not a free-tier assumption.

Evaluation questions before you commit

• Which of the advertised 80+ data sources does your stack actually need, and is each present in the Community Edition connector list?
• Who will run upgrades, backups, and patching for PostgreSQL, Redis, and the ToolJet containers, and how often do you realistically want to do it?
• Is AGPL-3.0 acceptable for how you deploy and who can access the system?
• Do you need GitSync, audit logs, embedded apps, or fine-grained permissions? If yes, is the ToolJet AI tier in budget?
• Are your servers ARM64, and have you confirmed image support beyond the linux/amd64 quickstart?
• Do SSO, data residency, or custom certificate requirements align with the documented setup, including the recent global certificate and RDS SSL changes?

When comparing alternatives, score them on the same variables: connector coverage, licensing, the free-versus-commercial feature boundary, deployment complexity, and who maintains the instance. Star counts and release velocity are useful signals but do not answer those questions.

Verdict

ToolJet looks like a maintained, practical open-source platform for teams that want self-hosted internal tools and workflow automation. The August 2026 snapshot shows frequent LTS releases, reported CVE patching, and steady component improvements, which are strong maintenance signals. My judgment, with conditions: pilot it if your connectors are covered and you can operate the stack; do not treat it as zero-maintenance, and do not assume enterprise capabilities are part of the community edition.

I’m Xiang Peng. At XP812 I help founders and operations teams evaluate platforms like ToolJet, plan deployments, and handle the upgrades, connectors, and maintenance that make them production-ready. If you want an independent review against your specific stack, I can give you a practical assessment and a plan.

Sources

• ToolJet/ToolJet repository and README (repository)
• v3.20.212-lts release notes (release)
• v3.21.60-beta release notes (release)
• v3.20.210-lts release notes (release)
• Amazon DocumentDB support request, issue #8370 (issue)
• ToolJet documentation (documentation)