Skip to main content
beton

ToolJet Pricing Teardown 2026

ToolJet went from one flat seat price to five cloud tiers, added AI credits to every plan, and kept AGPL — while Appsmith, the closest comparable, ships under Apache 2.0. That difference matters more than the per-seat number.

Vlad Nadymov
ToolJet Pricing Teardown 2026

Get every pricing teardown in your inbox

We tear down open-source pricing — what it really costs, what the license allows, whether it's worth paying for. No spam.

This post is a part of series on commercial open source software pricing. See full list of articles here.

ToolJet is the open-source internal-tool builder that shows up alongside Retool and Appsmith. Drag-and-drop frontend, 80+ data source connectors, built-in database, workflow automation. ~38k GitHub stars, v3.20 shipped May 2026 — not abandonware.

Plans

ToolJet’s cloud offering has five tiers as of mid-2026, up from three in earlier versions. All paid plans carry a 20% annual discount.

  • Free — $0: 2 builders, 50 end users, 2 apps, 100 AI credits/month. No Git sync, no SSO.
  • Starter — $19/builder/month: Same seat limits as Free (2 builders, 50 end users, 2 apps) but raises the AI allowance from 100 to 2,000 credits/builder, adds unlimited add-on credits, unlimited AI page generation, and 5 AI agents. Useful only to evaluate the AI builder without hitting the seat cap.
  • Pro — $79/builder/month: Unlimited builders, 100 end users, 5 apps, 2,000 AI credits/builder, unlimited AI agents, custom styling, version control, email support. The 5-app and 100-end-user caps bite most teams within months.
  • Team — $199/builder/month: Unlimited end users, unlimited apps, 2,000 AI credits/builder, SSO, custom user groups, white-labeling, Git sync, audit logs, modules. The production tier — the first plan where the per-seat price matches what you get.
  • Enterprise — custom: Adds SCIM provisioning, custom AI credit allocations, custom model integrations (bring your own LLM), dedicated support manager, optional expert services and training. Self-hosted Enterprise adds air-gapped deployment and multi-instance options.

Self-hosted tiers mirror cloud: Pro at $79/builder/month, Team at $199/builder/month, same feature gates; Enterprise custom.

The AI credits angle

Every paid tier ships 2,000 AI credits per builder per month (Free gets 100); Enterprise negotiates custom allocations and models. The agent builder — AI workflows that call data sources and trigger actions — is capped per tier: 2 agents on Free, 5 on Starter, unlimited on Pro, Team, and Enterprise.

AI credits as a billing dimension is new in 2026. Whether it becomes a real cost depends on how much your team uses AI app generation. Teams that mostly maintain existing tools won’t notice; teams shipping new apps regularly should size it.

The 5-app wall on Pro

Pro at $79/builder/month looks like the “real features” tier — version control, custom styling, email support. But 5 apps and 100 end users cap it. Five tools is not many: ticket dashboard, inventory tracker, onboarding form, support queue, data entry tool, and you’re done. Most production teams skip Pro and go straight to Team. Pro is effectively a long trial before committing to $199/builder.

License

ToolJet is AGPL-3.0 — the same license as Grafana’s core. Copyleft, with a network provision. What it means for internal tooling:

Running ToolJet privately for your own teams is fine. Modify it, extend it, self-host it — no code disclosure required, as long as you don’t distribute it externally.

The copyleft clause activates when you distribute a modified ToolJet as a product or service. An ISV that forks ToolJet and resells it as a white-labeled platform must open-source those modifications.

For enterprises using ToolJet as infrastructure, AGPL is not a problem. The Appsmith comparison is where it matters.

Appsmith is Apache 2.0: ~40k GitHub stars, comparable feature set, similar self-hosted/cloud split, $15/user/month Business tier. Apache 2.0 is permissive — fork it, modify it, ship a product on top, no obligation to open-source your changes. For a team building an internal-tools product (not just using one), Apache 2.0 removes a legal risk that AGPL introduces.

ToolJet and Appsmith are close enough on UX and features that the license is a real selection criterion. Not the only one — connectors, component library, self-hosting ops all matter — but beyond pure internal use, the license difference counts.

Worth paying for?

Free is a reasonable start for a solo developer or a team prototyping one or two tools. The 2-builder cap forces a decision the moment a second person starts building.

Starter at $19 is a narrow tier — AI credit flexibility, same hard caps as Free. Worth it only if AI generation is your specific bottleneck.

Team at $199/builder/month is the honest production price. Three builders is $597/month, roughly $7,200/year. Retool’s comparable tier (SSO, Git sync, unlimited apps and end users) runs similar or higher depending on end-user counts. Appsmith’s Enterprise for 100 users is $2,500/month — a per-user axis that favors ToolJet for orgs with many end users and few builders.

Self-hosting is a real cost-control option: self-hosted Pro and Team cost the same as cloud, but you own the infrastructure and data.

Enterprise is justified if you need SCIM, air-gapped deployment, or your own LLM models. Otherwise Team is the ceiling.


How ToolJet pricing scales

ToolJet bills per builder. Starter ($19) is AI-credit-focused; Team ($199/builder) is the real production tier (SSO, Git, audit logs) — a 10× per-builder jump.

$0$2,500$5,000$7,500$10,0001 builders5 builders10 builders25 builders50 buildersStarter $19/builderTeam $199/builder
Monthly cost as ToolJet scales by builder. Production features force the 10×-pricier Team tier.

This post is a part of series on commercial open source software pricing. See full list of articles here.

I build Beton — open source revenue intelligence for B2B SaaS.

Frequently asked questions

Is ToolJet open source?
Yes. The core is AGPL-3.0 licensed on GitHub (~38k stars). AGPL means you can self-host and modify freely for internal use, but if you distribute a modified version externally — as a product or service — those modifications must be open-sourced. Running ToolJet internally for your own teams does not trigger the copyleft clause.
What does ToolJet's Free tier actually include?
2 builder seats, 50 end users, 2 apps, and 100 AI credits per month. No SSO, no Git sync. Usable for a solo developer prototyping one internal tool; too constrained for a team shipping production apps.
What is the cheapest paid plan?
Starter at $19/builder/month (20% off billed annually). It keeps the same 2-builder/50-end-user/2-app limits as Free but jumps the AI allowance from 100 to 2,000 credits per builder, adds unlimited add-on credits, unlimited AI page generation, and 5 AI agents (Free gets 2). It is not the right tier for teams that need workflows or unlimited apps.
How does ToolJet's license differ from Appsmith's?
ToolJet is AGPL-3.0; Appsmith is Apache 2.0. AGPL is copyleft: if you distribute a modified version of ToolJet (e.g., build a product on top of it), you must open-source your modifications. Apache 2.0 has no such requirement. For pure internal use both licenses are fine. For ISVs or SaaS builders who want to fork and ship, Apache 2.0 is the more permissive choice.
What tier do most production teams land on?
Team at $199/builder/month. It is the first tier with unlimited end users, unlimited apps, SSO, custom user groups, white-labeling, Git sync, and audit logs — the table stakes for a real production deployment. Pro at $79 caps you at 100 end users and 5 apps, which most teams hit quickly.

Get posts like this in your inbox

Revenue intelligence, behavioral signals, and product-led growth. No spam.