Retool is my pick of the best internal tool builders if you want an admin panel on top of a database this week and you will pay per user. Appsmith is the better pick when you need to self-host or you want an open-source default before the seat invoice arrives. ToolJet is close to Appsmith. Try it when Appsmith's editor annoys you, not because a list told you there must be a single winner.
These products get expensive or messy at the same moment: when the internal tool becomes a product. If customers will see it, stop and write the real UI. I have watched a Retool app grow buttons until nobody knew which one charged a card.
The short answer
Retool for speed and polish. Appsmith to self-host. ToolJet if you are already comparing open-source builders and should spend one afternoon in both.
Top picks
Best internal tool builders
Tables, forms, and queries. The first screen is an afternoon. Permissions and environments exist so it is not only a demo. That first afternoon is why people standardize on it.
Widgets and queries against your databases and APIs, with a self-hosted path. For an internal admin that legal will not let a vendor see, that requirement ends the Retool cloud conversation.
A similar promise: build internal apps on your sources, self-host if you need to. The editor and the community are different enough that a one-screen pilot will tell you more than this paragraph.
What the best internal tool builders are good at
CRUD on a table your company already has. A support view of a user. A refund button with an audit log if you build the log. They are good at the screens engineers resent building and bad at the screens customers compare to your marketing site.
Write the permission check in the query, not only in the button you hid. Hidden buttons are how internal tools leak. I have clicked a hidden one by editing the frontend like a curious employee will.
Who should skip a builder
If the app is a single SQL report, a BI tool or even a saved query is enough. A builder is another system to permission.
If the workflow is a company-wide process with approvals, you may want a work tool, not a custom panel. Builders invite one-off logic that only the author understands.
How we tested Retool, Appsmith, and ToolJet
Last tested September 2026. I built the same internal screen in each: a searchable user table, a detail pane, and a button that wrote a note back to Postgres. Retool used its cloud. Appsmith and ToolJet ran with Docker on a MacBook Pro. I invited a second user and checked what they could click.
Retool was done first and looked like a product. Appsmith took longer and kept the database in my network, which was the requirement I cared about on the second day. ToolJet matched Appsmith's shape closely enough that I would decide on the query editor and the upgrade story, not on a feature matrix. The second user saw the button in all three until I fixed the query. The UI hide was not the control.
I did not test SSO beyond a basic setup, audit-log compliance, or apps with dozens of pages. Complexity in these builders compounds. If the screen needs a state machine, write code.