Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

Retool vs ToolJet: Internal Tool Builders Side by Side

For a company that wants a hosted internal tool platform with enterprise governance, AI app building and the option to bring in React code, Retool fits. For a team that wants an open source builder it can self-host for free, with a built-in database and end users priced inside the plan, ToolJet fits. The deciding factor is usually how many people will use your apps, not how many will build them.

ToolJet's repository has collected tens of thousands of GitHub stars, and my read is that it appeals to developers who like to see the code and run it themselves. Retool, by contrast, sells itself as a platform for production-ready internal apps, workflows and AI agents with governance built in. Both let a small team build admin panels and dashboards on top of their own data far faster than coding from scratch. Where they part ways is hosting, billing and how much control you keep.

My short take: if governance, security reviews and a large staff audience are the main concerns, Retool fits. If cost control, owning the code and running on your own servers come first, ToolJet earns the shortlist spot. The sections below show what each side does well, the situations where one clearly fits, and the billing detail that should settle the rest.

Where Retool comes out ahead

Retool's newest pitch is an AI app builder that produces internal apps ready for production use, with permissions and governance already in place. It can also import React code from tools such as Lovable and Replit, by ZIP file or GitHub sync, which is handy if someone on your team has prototyped an app elsewhere and wants to bring it inside the company's controls.

Its connector list is broad, covering databases, APIs and AI providers, from AlloyDB and Amazon's storage service to Anthropic and BigQuery. The docs cover both Retool-hosted and self-hosted deployments, plus a Retool API for automating admin tasks. At the Enterprise level you can run Retool Cloud, a self-hosted install or a fully air-gapped setup, which is often what a security team insists on before approving anything. If self-hosting is your deciding factor, Budibase and Retool for internal tools covers another open option.

There's also a free plan for small teams, with a pool of AI credits each month, so you can build a first app without a purchase order.

Where ToolJet comes out ahead

ToolJet is marketed as an open source, low-code AI app builder for internal tools, and you can host it on your own infrastructure starting free. For a startup with a developer who's comfortable with containers, that's a strong position: your data stays on your servers, and you aren't waiting on a sales call to begin.

It ships with a built-in no-code database running on PostgreSQL, so simple apps don't need a separate database at all, and it connects to more than a hundred databases, APIs and SaaS tools for everything else. ToolJet MCP lets coding agents such as Claude Code, Codex or Cursor build apps directly, without using ToolJet's own AI credits, which suits developers who already work that way. Extra AI credits can be bought pay-as-you-go if you use the built-in assistant heavily.

If you'd like to see how both sit against the rest of the category, my guide to the best low-code platforms covers the wider field.

Which one fits your situation

A two-person ops team building a handful of tools for themselves: either works, and I'd lean towards whichever free plan covers your users. ToolJet's free self-hosted route costs nothing but your time; Retool's free plan gets you running without a server to look after.

A company where a few builders make apps for a large group of staff who only view or update records: this is where the meters matter most. Retool charges a lower rate for internal users than for builders, so a big audience still adds cost per head. ToolJet charges per builder and caps end users by plan, with unlimited end users only on Enterprise, so a large audience pushes you up the tiers instead.

A regulated business that needs air-gapped hosting, audit logs and single sign-on: Retool's Enterprise options were built for this, and ToolJet's higher plans also add SSO and audit logs. Ask both for their security documentation before you shortlist.

A developer-led team that wants to own the stack and build with coding agents: ToolJet's open source core and MCP route will feel at home. And a team that has already prototyped in Lovable or Replit will appreciate Retool's React import.

Two meters that change the bill

Retool bills per builder each month and adds a separate charge for each internal user, with different rates for builders and users on each tier. On Business, someone counts as a builder only if they created or edited an app or workflow that billing cycle, so view-only staff are priced at the cheaper user rate. That's fair, though it means your bill moves with how many people touch an app.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

ToolJet bills per builder and sets a ceiling on end users and apps for each plan, with Cloud and Self-Hosted pricing shown on separate tabs. Unlimited end users with no per-user fees appear only on Enterprise. So for a small builder team serving a modest audience, ToolJet can be simpler to predict; for a huge audience, the jump to Enterprise is the figure to ask about. Both vendors publish current numbers on their pricing page, and it's worth modelling your own builder and user counts on each.

Feature gaps on the lower tiers

Plan features differ in ways that matter to growing teams. On Retool, Git source control, SSO with SCIM and two-factor, and audit logs aren't on the Free or Team plans, so you'll need Business or above for them. On ToolJet, the higher plans add version control, SSO, white labelling, audit logs and Git sync, and support on the lower plans is community help through Slack.

These gaps decide which tier you'll really need. If your IT team requires single sign-on from day one, price the plan that includes it, not the entry plan, on both sites.

There are softer limits too. In my view, Retool's governance depth, from audit logs to air-gapped hosting, is more than a team needs if it only wants a quick form over a spreadsheet. ToolJet's self-hosted route is free in licence terms, yet someone still has to patch, back up and upgrade the server, and that time is a real cost even when no invoice arrives. Weigh who on your team will own the platform after launch, not just who will build the first app.

Do you make internal tool builders and low-code app platforms? Tool makers can ask to be considered for a featured place on this list.

Moving apps from one to the other

Retool can import React code via ZIP or GitHub, but I found no ToolJet app importer on either site, so expect apps to move by being rebuilt rather than converted. The encouraging part is that both vendors list self-hosting and connect to databases and APIs directly, so your data sources can be re-pointed rather than migrated. Your tables don't move; only the interface layer is rebuilt.

Start with the simplest, most-used app, rebuild it on the new platform, and run both for a short spell so users can compare. Keep a list of every query and permission rule in the old app, because those are the details people forget. If you're weighing more options before switching, my roundup of Retool alternatives lists other builders worth a look.

A refund-request panel as the shortlist exercise

Pick a real task, such as an admin panel for refund requests: a table of open requests from your database, a form to approve or reject one, and a status that updates on save. Build it in Retool's free plan, then build it again in ToolJet, either on the cloud free plan or self-hosted with its built-in PostgreSQL database.

Score each build on four things:

  • How long the database connection took to set up.
  • How easily you could limit approvals to managers only.
  • How the AI builder handled a plain-English request such as "add a filter for requests older than a week".
  • How a view-only colleague is counted on the billing screen once invited.

That last point tells you more about long-term cost than any feature grid, because it shows which meter your real audience will run up.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.