Today, we’re releasing ToolJet 4.0, our biggest release so far.
The biggest addition is React Builder. You can now build the entire frontend of a ToolJet app in React, including with the coding agents and editors you already use. We’ve also substantially updated the Visual Builder, with three new UI packs.
We want both ways of building to work well. A visual builder is useful when you want to put together an app quickly and make changes directly on the canvas. React gives you more room when the interface needs something the existing components don’t provide.
The choice shouldn’t require moving your application to another platform. With 4.0, you choose how to build the frontend and continue using ToolJet for data connections, queries, access control, and deployment.
React Builder
Until now, the visual canvas has defined how you build a ToolJet app. React Builder opens up a different approach: the frontend is React code that you can inspect and edit.
You can start by describing the app to ToolJet AI, then work on the generated result. The style inspector lets you adjust the interface inside ToolJet. For changes you’d rather make in code, you can edit the source or work locally in VS Code or Cursor using the ToolJet extension and local development tools.
This is particularly useful for apps with detailed interactions: a support console with several connected panels, for example, or a scheduling interface that doesn’t fit neatly into a table and a form.
Claude Code and Codex are also part of how you can build with ToolJet. Our existing MCP tooling supports app authoring from coding agents, while the local React tools let you work directly on the frontend in your editor.
You choose Visual Builder or React Builder when creating an app. These are two separate builders; we aren’t promising automatic conversion between them.
Three new UI packs for Visual Builder
We’re continuing to invest in the visual experience. Being able to select a component and change it directly is still useful, even when AI wrote the first version of the app.
The new UI packs are Rocket 2.0, based on shadcn; Ant Design; and Material UI (MUI). They give builders more choice over the components and appearance of their applications.
You can use AI to generate the app, then continue editing on the canvas. For someone maintaining a tool their team uses every day, that ability to make a small change without digging through frontend code matters.
Inspect changes before releasing them
AI can make a lot of changes in one turn. We wanted a better way to look through the result.
With visual diff, you can compare what changed after an AI turn or between versions of an app. The slider view lets you compare the interfaces directly. If an app edit isn’t right, you can revert it using undo.
We’ve also added review requests and comments. A builder can ask someone else to review a version, discuss the changes, and resolve comments before release. Teams that need a formal approval process can configure mandatory approvals for promotion between environments.
These features belong together. The reviewer needs to see the actual change, and the team needs a way to make the review part of releasing the application.
Security checks for React apps
A generated frontend can look right and still depend on an npm package with a known vulnerability. That’s one of the things we want builders to catch before the app goes into use.
App security scanning checks React app dependencies for known vulnerabilities. You can inspect the findings and use organization-level security policies to govern how they’re handled. You’ll still need to review the application’s permissions and business logic; dependency scanning covers a specific part of that work.
Human approvals in Workflows
ToolJet Workflows on Self-hosted now supports human-in-the-loop approvals. Add an approval step, and the workflow pauses until a person approves or rejects the request.
For a refund process, that could mean collecting the order details and preparing a recommendation automatically, then waiting for a support manager before issuing the refund. The approved and rejected decisions can follow different paths.
It’s a way to automate the work around a decision while keeping the decision itself with a person.
AI usage limits and updated allowances
Administrators can now set AI credit limits per builder. As more people use AI to build apps, this gives the organization control over individual usage.
We’re also updating plan allowances for this release. Plan names and prices stay the same. The pricing page has the limits and feature availability for each plan and deployment.
Try ToolJet 4.0
You can create an account to get started, or book a demo if you’d like us to walk through your use case.
If you self-host ToolJet, please read the 4.0 migration guide before upgrading. There are changes to environments, GitSync, and app behavior that need attention. Back up your deployment and test in staging first.
Thank you to everyone who tested the beta and sent us feedback. And thank you to the team for the work that went into this release.
I’m particularly excited to see the applications people build with React that would have been difficult to build in ToolJet before. Expanding what you can build, while keeping the parts of ToolJet you already rely on, is what makes this release important to us.
Navaneeth
Founder & CEO, ToolJet









