Retool Pricing in 2026: Plans, Tiers, and What Buyers Actually Pay

Retool pricing tiers, and what each one includes

Retool's pricing page lists four tiers, each priced around two user types: Standard Users (the people building apps) and Internal or External Users (the people using them).

• Free: $0. Up to 5 users, unlimited web and mobile apps, unlimited database management, 500 workflow runs per month.
• Team: Builder: $10/month (annual) or $12/month (monthly). Internal user: $5/month (annual) or $7/month (monthly). Up to 100 users, 5,000 workflow runs per month, staging environment, app release versions.
• Business: Builder: $50/month (annual) or $65/month (monthly). Internal user: $15/month (annual) or $18/month (monthly). Up to 100 users, audit logging, portals and embedded apps, unlimited resource environments, custom branding.
• Enterprise: Custom quote. Everything in Business plus SSO/SCIM, 2FA enforcement, streaming audit logs, source control, air-gapped self-hosted deployment, and up to 6 instances.

On the Business tier, external users (customers or partners using an embedded app) are billed separately on a tiered scale: the first 50 per month are free, then $8/month each (annual) from 51 to 250, $6/month from 251 to 500, and $4/month past 500. Retool's billing documentation confirms this external-user structure took effect on September 13, 2025, and that mid-cycle additions aren't prorated: an internal user upgraded to builder partway through a month is billed at the builder rate for that period regardless of when the upgrade happened.

Three allowances sit underneath those seat rates and are easy to miss when you compare tiers. Checked on retool.com/pricing on September 18, 2026: the Free tier carries 5GB of database capacity, 5GB of file storage, up to 20 hours a month of Agents and 250 AI credits a month. Team carries 1,000 AI credits a month, described on the page as 750 plus a 250 bonus. Business carries 3,000, described as 1,500 plus a 1,500 bonus. Enterprise is listed as 1,000 credits per builder plus a 4,000 pooled allowance. Every tier gets the same 20 free agent hours.

Retool is also running a dated promotion worth knowing about if you are already in a procurement cycle: customers who sign an Enterprise contract by September 30, 2026 get AI credits the page values at up to $10,000 per year of the contract term.

What real buyers actually pay

Published tiers describe the sticker price. Vendr's marketplace data, drawn from 158 actual purchases and checked on September 18, 2026, puts the median Retool buyer at $65,500 per year, with an average negotiated discount of 19% off list. The observed range runs from about $24,700 at the low end to $152,500 at the high end.

Vendr refreshes these figures as new contracts land, so the exact median moves. It sat at $64,623 across 156 purchases earlier in 2026. The shape of the number is the durable part: a five-figure median, a six-figure ceiling, and a floor well above what the per-seat rates imply.

The gap between a $10/month list price and a $65,500/year median bill comes from how the seat math compounds. A team with 5 builders and 20 internal users on the Business tier is already at $50 x 5 + $15 x 20 = $550/month before adding workflow overages, End User packs, or self-hosted infrastructure. Vendr's own notes on the deal data point to the same drivers: Standard User count, End User volume, and self-hosted add-ons are what separate a small team's bill from an enterprise one.

How Retool's seat model actually bills you

The single most misread thing about Retool pricing is what makes someone a builder. It is not a seat an admin assigns. On Free, Team and Business it is a behaviour, measured per billing cycle.

Retool's billing docs define a builder as an enabled user who built or edited an app or workflow during the billing cycle, and an internal user as an enabled user who did not. The docs spell out the consequence directly: a user with edit permissions who has not edited anything in a while counts as an internal user for billing that month. Flip it around and the risk is obvious. Anyone with edit rights who opens an app and changes one label becomes a builder for that whole cycle, at five times the internal rate on Business, and the change is not prorated.

That creates a bill that moves with behaviour rather than headcount. Take a 30-person Retool org on Business annual:

Same 30 people, same apps, a $420 per month swing. Assumptions: Business annual rates, Retool Cloud, no external users, no overages.

The fix is permission groups, which restrict who can edit so those users stay at the internal rate. Retool's docs are explicit that this control is available on Business and Enterprise. On Team you have the cheaper rates but no way to stop the drift, and on Free everyone is free anyway. So the tier with the most money exposed to seat drift is also the only self-serve tier that can prevent it, which is worth building into your rollout rather than discovering in month three.

Annual commitments have their own asymmetry. You prepay a quantity of builders and internal users. Going over is billed monthly at the monthly rate, which is higher than the annual rate you locked in. Going under refunds nothing: Retool's docs say you can add users to an annual commitment by contacting support but cannot subtract them, and cancelling does not produce a prorated refund for unused time. Estimate low and pay the monthly rate on the overage rather than estimating high.

What the sticker price leaves out

Seats are the headline. These four line items are where a modelled budget and a real invoice separate. All figures verified on Retool's pricing page and billing docs on September 18, 2026.

Two details inside that table deserve their own sentence.

First, external users scale into real money faster than the per-unit rates suggest. Retool's billing docs work through an example of an annual Business plan with 510 external users: the first 50 free, the next 200 at $8, the next 250 at $6, the final 10 at $4, for $3,140 a month. That is $37,680 a year on external users alone, on top of every builder and internal seat, and it is a portal most teams would describe as mid-sized.

Second, agent time bills even when it fails. Retool's agents billing documentation states that all agent runtime counts toward the hourly allocation, including runs where the agent does not complete the task. Retool's model here is deliberate and it argues the case openly: hourly pricing is meant to mirror how teams already value labour. It also means a misconfigured agent that loops for an hour costs the same as one that works.

On AI credits, Retool publishes a conversion that makes the allowance legible. Each AI prompt uses about 12 credits, a typical app takes 3 to 6 prompts, and the Business allowance covers 36 to 84 apps a month. Credits are pooled across the organisation and renew monthly without rolling over, so an unused allowance is gone rather than banked.

What changed with self-hosting

Self-hosting used to be one of Retool's selling points: run it in your own VPC, keep data in house, avoid vendor lock-in. That is now Enterprise only, and Retool has said so in its own words.

Switch the toggle on retool.com/pricing from Cloud to Self-host and the page answers the question without ambiguity. Verified on September 18, 2026: the Free, Team and Business cards all replace their call to action with the line "Plan not available on Self-host", and in the Compare Features table below, every row for those three tiers renders as a dash. Only the Enterprise column carries values. The FAQ on the same page says Enterprise plans support both deployment options.

That contradiction is exactly what surfaced in a r/selfhosted thread titled "Retool disables self-hosted pricing plans", which links to a Retool community forum post titled "Self-hosted docs now state Enterprise-only." Commenters describe the change as quiet rather than announced: no changelog entry, just updated docs. One reply summarized the pattern bluntly: offer self-hosting to build trust and adoption, then move it behind the highest tier once enough customers are locked in. Whether or not that's the intent, the practical effect for a buyer today is the same: a serious self-hosted deployment now routes through Retool's Enterprise sales team, not a self-serve tier.

What Retool itself said, and when

The community forum thread is the most useful record of the change, because Retool staff answered in it. The sequence, read on September 18, 2026:

• February 18, 2026. A user posts that the documentation now says self-hosted is Enterprise only, and asks whether an existing personal deployment will keep receiving updates. No announcement had been made.
• February 19. Another user reports that registering a new self-hosted licence at my.retool now redirects to the pricing page, which at that point still showed self-host plans matching cloud, and notes that different Retool pages were saying different things.
• February 19. A Retool staff member replies that the company is no longer accepting new self-hosted signups through the self-serve channel, describes the docs update as part of broader plan adjustments planned for later in the year, and says details for existing self-hosted accounts are still being finalised.
• The reply marked as the thread's solution. A Retool staff member apologises for the handling, saying customers should have heard it directly rather than seeing it in the docs, and gives the reason: self-hosting carries infrastructure, security and compliance weight the company concluded it can only support properly through its Enterprise offering.

The same reply makes three commitments that matter to anyone already self-hosting. Existing deployments keep running with unchanged capabilities, and this is not an end-of-life announcement. There are no current plans to sunset legacy self-hosted plans. If that ever changes, Retool says it will give at least six months of advance notice.

What this means for your deployment

For a buyer today, the decision tree is short.

Already self-hosted on a self-serve plan. Nothing to do right now. Retool has committed publicly to six months of notice before any sunset, which is enough time to migrate. The thing worth doing is writing down what your migration would cost, so the answer exists before you need it.

Planning a new self-hosted deployment. Budget for Enterprise. There is no self-serve path, the licence registration flow does not lead anywhere, and pricing is a conversation rather than a number. Get the quote scoped to the specific compliance requirement driving the self-host decision, because that requirement is the only thing making Enterprise mandatory.

Self-hosting is a preference, not a requirement. This is where the change genuinely costs you, and where the open-source options below get interesting. If the driver was cost control or philosophy rather than a rule an auditor enforces, Retool Cloud on Business plus a serious look at Appsmith or Budibase is a more honest shortlist than an Enterprise quote.

Agency or consultancy recommending Retool to clients. The forum thread's most-upvoted complaint is precisely this case: engagements planned a year out around an assumption that stopped being true overnight. If you are in that position, the risk to manage is not the price, it is committing a client to a deployment model whose availability you do not control.

Retool vs Superblocks, Appsmith, Budibase, and building it yourself

Retool is the most expensive obvious option and the most complete one. Here is how the entry pricing compares, all figures read from each vendor's own pricing page on September 18, 2026.

A few things that table flattens and shouldn't.

Superblocks prices its Teams plan at $100 per month on annual billing and $125 on monthly, scoped on the page to 15 builders and one hosted app, with additional apps at $10 each per month. It includes 100 Governed Agent Units a month for its Clark AI agent and 50+ integrations, with a 14-day trial. Vendr's Superblocks data puts the median buyer at $20,448 a year against a $4,362 to $169,630 range, which is roughly a third of Retool's median. Read that as positioning rather than a like-for-like discount: the range ceiling is higher than Retool's, so the large deals exist, there are just fewer of them.

Appsmith is the cleanest per-seat comparison, at $15 per user per month on Business with no builder and viewer split. That single rate is either much cheaper or slightly more expensive than Retool's Business tier depending entirely on your builder-to-viewer ratio: at 5 builders and 60 viewers, Appsmith's flat $15 costs $975 a month against Retool's $1,150, but at 5 builders and 15 viewers it is $300 against $475. Appsmith's Enterprise tier is published at $2,500 a month for 100 users, which is unusual in this category and makes budgeting past 100 seats straightforward.

Budibase is the option that most directly answers what Retool just stopped doing. Its open-source self-hosted plan is free indefinitely with unlimited apps, automations, agents and users on one workspace, and its FAQ says so in those terms. Paid cloud starts at $19 a month, and the paid dimension is actions rather than seats, with end users at $5 each a month and additional creators at $50 each on yearly billing.

Building it yourself is the comparison everyone skips and it deserves a number. The US Bureau of Labor Statistics puts the median annual wage for software developers at $135,980 as of May 2025. Divide by 2,080 hours and an engineer-hour costs $65.37 before any benefits, payroll tax, equipment or management overhead. Every real employer pays more, so treat $65 as a hard floor rather than an estimate.

Run that against a mid-sized Retool bill. Eight builders and 60 internal users on Business annual is $1,300 a month, or $15,600 a year, which buys about 239 engineer-hours at the floor rate. The question is not whether you could build a few internal dashboards in 239 hours. You could. The question is whether you could build them, host them, authenticate them, add role-based permissions, keep them running when the upstream API changes, and still have hours left for the next request. For teams with a handful of stable tools the build is genuinely cheaper. For teams fielding a steady queue of requests it is not close, because the 239 hours has to cover maintenance forever, not just the first version.

Worked scenarios for four team shapes

Assumptions for all four: Retool Cloud, annual billing, list prices with no negotiated discount, and no AI credit packs. These are my models, not Retool's or Vendr's, and they exist to show which variable moves your bill.

Scenario 1: small ops team, internal only. Three builders and 12 internal users, no portal, workflow usage inside the included 5,000 runs.

The $2,880 a year difference buys audit logging, permission controls, portals and custom branding. If none of those are requirements yet, Team is the correct answer and the upgrade can wait until one of them becomes a blocker.

Scenario 2: growing engineering org. Eight builders and 60 internal users on Business annual, still inside the workflow allowance.

Eight builders at $50 is $400, sixty internal users at $15 is $900, total $1,300 a month or $15,600 a year. This is the shape where the builder definition starts to matter: if 14 of those 60 internal users edit something in a given month, the same team costs $1,600 that month instead. Permission groups are the difference.

Scenario 3: customer-facing portal. Five builders, 10 internal users, 510 external users on Business annual, using Retool's own external-user example.

$42,480 a year, and 89% of it is external users. Any portal with a growing audience needs this modelled before the Business plan is signed, not after.

Scenario 4: automation-heavy team. Four builders, 20 internal users, 25,000 workflow runs a month on Business annual.

Four builders at $50 is $200. Twenty internal users at $15 is $300. Workflow runs are 5,000 included plus 20,000 extra, which is four blocks at $75, so $300. Total $800 a month or $9,600 a year, and more than a third of it is workflow overage. Teams in this shape should compare against dedicated automation tooling rather than assuming Retool is the cheapest home for the work. Our breakdowns of n8n pricing and the Zapier alternatives worth considering cover that side of the market.

None of these four scenarios reaches Vendr's $65,500 median, which is the point. The median includes Enterprise contracts with self-hosted deployments, premium support and much larger seat counts. Vendr's own description of the pricing basis names exactly those drivers. If your modelled number is $10,000 and the median is $65,500, you are probably modelling correctly and simply buying a smaller deployment than the median buyer.

Who Retool is genuinely wrong for

Retool is a good product and the market share reflects that. It is still the wrong choice in five specific situations, and a comparison page that will not say so is not worth reading.

You need self-hosting and cannot fund Enterprise. This is the clearest case and it is new as of 2026. Budibase's open-source tier is free and unlimited on users; Appsmith ships a self-hostable open-source edition too. Either is a better starting point than an Enterprise quote you cannot justify.

You need vendor support without an Enterprise contract. Retool's own feature comparison lists technical support from its support engineering team as Enterprise only, with a dash against Free, Team and Business. Paying $50 per builder per month and still having no support path surprises people.

You need Git-based source control below Enterprise. Source control with branch-based editing is Enterprise only on Retool's comparison table. Appsmith includes Git version control on its free tier, capped at three repos. If reviewable, branch-based changes are part of how your team works, that gap will bite early.

Your user base is mostly viewers and your builder count is tiny. Retool's split-rate model is designed for this and usually wins. But once viewers run into the hundreds, compare carefully against Appsmith's flat $15 and Budibase's $5 end-user add-on, because a flat rate can beat a discounted rate at volume.

What you actually need is AI access to your systems, not another app to log into. If the request behind the internal tool is "someone needs to look up a customer record" rather than "someone needs a dashboard", building an app is a heavier answer than the question deserves. That is the case the next section is about.

What buyers should ask before signing

Three questions come up repeatedly across independent pricing writeups and the Vendr benchmarking data:

First, model the External User tiers before committing to a Business plan if the app has any customer-facing or partner-facing use. The free allowance is 50 users per month; past that, the per-user rate scales down as volume grows, but a portal that grows past a few hundred external users changes the bill meaningfully.

Second, ask directly whether self-hosting is actually required for the deployment, and if so, get Enterprise pricing scoped to that specific need rather than assuming the lower tiers still cover it. The gap between what the marketing FAQ implies and what the feature table shows is exactly the kind of thing that surfaces after a team has already built on a lower tier.

Third, treat the 19% average discount in Vendr's data as a starting point for negotiation, not a ceiling. Buyers who come in with a competing quote or a clear multi-year usage estimate tend to land below the median more often than buyers who accept the first number.

Four more that come straight out of the billing mechanics above, and that most comparison pages never mention:

Ask what happens to your builder count in a month when a lot of people happen to edit something, and get the permission-group configuration agreed during onboarding rather than after the first surprising invoice. Ask for the workflow run forecast in writing, because $75 per 5,000 runs compounds quietly. Ask whether agent hours are in scope at all, given they bill separately from AI credits and count failed runs. And if you are signing before September 30, 2026, ask for the Enterprise AI credit promotion explicitly rather than assuming it is applied.

How Retool's pricing compares to the category

UI Bakery's independent pricing breakdown, published August 2026, and Vendr's own head-to-head data both place Retool in the middle of the internal-tools-builder category on a per-seat basis: Airplane's typical range runs $20 to $40 per user per month against Retool's $10 to $50, while Superblocks runs higher still at $30 to $60. None of the three publish a single number that covers a real deployment; all three require modeling builder count, end-user volume, and any self-hosted requirement to get to an actual budget figure.

The category-level pattern worth noticing is that per-seat rates have converged while the things around them have not. Entry pricing across Retool, Appsmith and Budibase sits in a band from $15 to $50 per builder-equivalent. What actually separates the bills is deployment model, usage allowances and end-user volume, which is why two companies with identical headcounts routinely land $40,000 apart. Our enterprise AI price index tracks the same effect across the AI tooling category, where published per-seat rates have converged and total cost has not.

What this means if you're comparing options

Retool, Airplane, and Superblocks solve the same problem: building internal tools and apps on top of existing data sources, with a person doing the building. That's a different problem from giving AI tools like Claude or ChatGPT governed access to those same data sources and systems, which is what Coworker MCP does.

Comparing the two isn't really an either/or. A team might use Retool to build an internal ops dashboard and separately want an AI agent to be able to look up a customer record in Salesforce or update a ticket in Jira without a human opening an app at all. Coworker MCP connects AI tools to 50+ apps through one governed connection, at Coworker's own published pricing: Pro at $29.99/month, Max at $149.99/month, and custom pricing for enterprise deployments, with no seat math to model before knowing what a deployment costs. See how AI pricing models compare across the category, how to choose the right MCP server for your team, or what enterprise MCP deployment actually requires if governance is the open question. If you are earlier in the evaluation, the no-code AI tools landscape and the workflow automation tools worth comparing cover the adjacent categories.

Book a demo to see Coworker MCP's actual pricing, no seat calculator required.

Frequently asked questions

How much does Retool cost?

Retool's list price starts at $10/month per builder plus $5/month per internal user on the Team tier, but based on Vendr's purchase data from 158 buyers, the median actual annual spend is $65,500, ranging from about $24,700 to $152,500 depending on team size and usage.

What are Retool's pricing tiers?

Four tiers: Free ($0, up to 5 users), Team ($10/builder + $5/internal user per month, annual billing), Business ($50/builder + $15/internal user per month, annual billing), and Enterprise (custom quote, required for full self-hosting and SSO).

Can you still self-host Retool for free?

No. With the Self-host toggle selected on Retool's pricing page, the Free, Team and Business plans all display "Plan not available on Self-host" and every feature row for those tiers renders as a dash. Only Enterprise remains. A Retool staff member confirmed in the company's community forum in February 2026 that new self-hosted signups through the self-serve channel had stopped.

What happens to an existing self-hosted Retool deployment?

According to Retool's own reply in that forum thread, nothing immediately. Existing deployments keep running with unchanged capabilities, it was not framed as an end-of-life announcement, and the company said there are no current plans to sunset legacy self-hosted plans and that it would give at least six months of advance notice if that changed.

Is Retool pricing negotiable?

Yes. Vendr's data shows buyers save an average of 19% off list price, and larger deployments with multi-year or annual commitments tend to see the biggest discounts.

What counts as a builder in Retool's billing?

Behaviour, not a seat assignment. Retool's billing docs define a builder as an enabled user who built or edited an app or workflow during the billing cycle, and an internal user as one who did not. Editing a single app once in a month moves someone to the builder rate for that whole cycle, and the change is not prorated. Business and Enterprise plans can use permission groups to restrict editing and hold users at the internal rate.

What's the difference between Standard Users and Internal/External Users in Retool's pricing?

Standard Users are builders who create apps, priced highest ($10-$50/month depending on tier). Internal Users are people inside the organization using finished apps, priced lower ($5-$15/month). External Users are customers or partners accessing embedded or portal apps, priced on a separate tiered scale starting free for the first 50 per month.

How much do extra Retool workflow runs cost?

Free includes 500 runs a month and Team and Business both include 5,000. Beyond that, additional runs are sold at $75 per 5,000 runs per month. A team running 25,000 runs a month on Business pays $300 a month in overage, which can exceed the seat cost on a small team.

Does Retool charge separately for AI?

Partly. AI credits are included in every tier (250 on Free, 1,000 on Team, 3,000 on Business), pool across the organisation, renew monthly and do not roll over, with extra packs sold to paid plans. Agents are billed separately by the hour, do not draw from the credit pool, and come with up to 20 free hours a month. Retool's docs note that all agent runtime bills, including runs that fail to complete the task.

Is Retool cheaper than Appsmith or Budibase?

Usually not on list price. Appsmith charges a flat $15 per user per month on Business and publishes Enterprise at $2,500 a month for 100 users. Budibase starts at $19 a month and offers a free, unlimited-user open-source self-hosted plan. Retool is more expensive per seat and considerably more capable, and it is the only one of the three that no longer offers self-hosting below its Enterprise tier.

Is there a published-pricing alternative to Retool for AI tool access?

If the actual need is connecting AI assistants to company systems and data rather than building internal apps, Coworker MCP publishes its pricing directly (Pro $29.99/month, Max $149.99/month, custom for enterprise) and connects to 50+ apps through a single MCP connection, without the seat-and-usage modeling Retool's tiers require.

Related reading

• Enterprise AI Pricing Compared
• How to Choose MCP Servers for Your Team
• What Enterprise MCP Deployment Requires
• The Enterprise AI Price Index
• Best AI Workflow Automation Tools