Retool pricing includes Free, Team, Business, and quoted Enterprise plans. Retool’s official price sheet lists Team at $12 per builder and $7 per internal user per month, or $10 and $5 with annual billing. Business is $65 per builder and $18 per internal user monthly, or $50 and $15 with annual billing. These are US cloud subscription rates, before additional usage and implementation work.
For an internal app budget, count the people who build it separately from the people who use it. Then add the cost of connecting records, testing access, and maintaining the result. Permute publishes this breakdown and sells connected business data and custom software with managed delivery. The comparison is between owning the build and buying a supported implementation, so price both against the same app requirement.
Retool plans and user rates
Rates below were checked October 7, 2026. Annual rates are monthly equivalents for an upfront annual commitment; they do not mean you can buy a single month at that price. Confirm your billing currency, contract, and selected features before purchase.
| Cloud plan | Monthly billing: builder / internal user | Annual billing: builder / internal user | Production fit to check |
|---|---|---|---|
| Free | $0 / $0 | $0 / $0 | Up to 5 users; evaluation or a small app |
| Team | $12 / $7 per month | $10 / $5 per month equivalent | Staging and production for growing teams |
| Business | $65 / $18 per month | $50 / $15 per month equivalent | Audit logs, richer permissions, external apps |
| Enterprise | Quoted | Quoted | Advanced identity, source control, deployment, and support |
Use Retool’s live plan comparison to check the features your production app requires. A Team subscription and a Business subscription serve different access and release requirements. If those requirements change the decision, compare the Retool alternatives for internal tools alongside the license bill.
Who counts as a builder or an internal user?
Retool’s billing documentation classifies enabled users on Free, Team, and Business by their activity during the billing cycle. Users who build or edit an app or workflow count as builders. Enabled users who do not build or edit count as internal users at the lower rate. A person who edits during that cycle can therefore change the user-rate calculation.
Budget separate cohorts. If your controller uses a dashboard and your developer changes its queries, they perform different jobs and may incur different rates. Review editing permissions before launch so a person who needs to consume an app is not granted development access by habit. Enterprise contracts can use assigned seat types, so confirm their definitions in the quote.
The billing docs say user additions within a cycle are not prorated. Annual plans prepay a quantity of each user type, with usage above that commitment billed at monthly rates. Keep a record of expected builders and internal users (two distinct groups) before committing to a year, then review changes with the billing owner.
A cost example for three builders and twenty users
Assume 3 builders and 20 additional internal users, for 23 people in total. Using Retool’s published annual rates, the Team estimate is 3 × $10 + 20 × $5 = $130 per month equivalent, or $1,560 for the annual seat commitment. The Business estimate is 3 × $50 + 20 × $15 = $450 per month equivalent, or $5,400 annually. This is a calculation from the rates above, not a vendor quote.
These estimates exclude taxes, discounts, extra usage, and app delivery. Select the required controls first, then calculate the plan that supplies them. A lower-rate plan is useful only if the proposed app can operate within its features; ask the implementation owner to identify what would force a change of tier.
$130/mo
Annual seat commitment: $1,560
$450/mo
Annual seat commitment: $5,400
$320/mo
Annual difference: $3,840
External users, workflows, and AI add to the bill
Customer or vendor portals need a separate external-user estimate. Retool’s billing documentation includes 50 external users per month at no cost for Cloud Business, followed by tiered charges. Model the people expected to access the portal during a billing cycle, and ask for the external-user terms when requesting an Enterprise quote. Employee seats alone do not price a customer-facing app.
Retool’s workflow billing documentation counts successful triggered runs as billable. Failed runs and manual tests in the Workflow IDE are nonbillable. The price sheet includes 500 runs per month on Free and 5,000 on Team and Business, with additional runs listed at $75 per 5,000. Estimate scheduled refreshes and event-driven runs using your workload, including nested workflows.
Retool’s AI credit documentation describes an organization-wide pool for AI features that renews each cycle and does not roll over. Builders share the allowance. Published materials distinguish base and promotional credits, so confirm the current allocation in billing settings instead of budgeting around a temporary bonus. Paid plans can purchase additional packs.
Retool Agents billing is separate from the AI credit pool and depends on runtime and model. Failed agent tasks can still accrue billable time, while waiting for human approval or resource authentication is excluded. Test representative tasks and review measured runtime before estimating production usage. A subscription paid annually can still have monthly usage overages.
Required controls can determine the plan
The live pricing page places audit logs and rich permission controls in Business, with source control and advanced identity controls in Enterprise. It lists cloud, self-hosted, and air-gapped deployment for Enterprise. Confirm the deployment in writing when requesting a quote, particularly if a previous plan or older documentation showed different availability.
Write down the access test your app must pass. A property manager might be allowed to see one building while finance sees the portfolio. A hidden button does not establish that the backend denies other records. Your builder must configure the appropriate access checks and demonstrate them before production use, regardless of the plan you purchase.
Budget the work around the subscription
Assign someone to connect the records and maintain the app. A construction cost screen needs agreed project IDs and cost definitions before its total can match the finance report. An inventory review needs a defined treatment of adjustments and open orders. The software cannot choose those rules on behalf of your finance or operations owner.
Request a build estimate that includes queries, access tests, and release checks. Add support for source changes and failed refreshes after launch. If you self-host, include infrastructure upgrades and recovery work. The enterprise app development process gives you the delivery steps to attach to that estimate.
Permute: price a supported implementation
Permute sells connected business data and custom software with managed delivery. We connect approved sources, match records, and apply the reporting rules your team approves. The calculations can be reused across dashboards and apps, with source evidence behind the figures. Our engineers build and maintain the work covered by the engagement.
For a controller, that can mean the job-cost app and management report use the same prepared records and calculation. Your team approves the cost definition; we implement it and preserve the path back to source. Compare custom software with delivery support against staffing and maintaining a build yourself, using the same sources and outputs in each scope.
Permute pricing combines a subscription with implementation and support scoped to the work. Typical scoped implementations go live in weeks, starting with the connections and report you need first. See Permute pricing, then request a delivery scope that covers source access, calculations, app releases, and ongoing support. Compare the complete budgets, not two subscription prices.
Explore shared business data
See how connected records and reusable calculations can support reporting and internal apps.
Confirm scope before treating the app as delivered
Software access and implementation support are different purchases. Confirm who builds the required workflows, who checks the results, and what ongoing service is included. Your business owner still decides definitions and exceptions, and your technical owner needs a release and recovery plan.
Permute hosted apps use externally compiled static frontends with permissioned queries and configured actions. Hosted builds, source editing, and general server runtimes remain outside that scope. Confirm any required action or ERP write path before agreeing to delivery; blanket write-back is not implied. Claude, ChatGPT, and other coding tools remain choices for building the interface.
Estimate the builder and internal-user cohorts for the app you need, then choose the plan that meets its production controls. Add external users and measured usage to that license estimate. Attach a build and maintenance budget with named owners for data, access, and support. The decision is whether your team can deliver and operate the app within that complete budget.
Compare the full delivery cost
Scope one internal app, its data connections, and the support needed after launch.
Questions about Retool pricing
How should I compare an Enterprise quote with published rates?
Ask for the seat definitions, included usage, and deployment terms in the quote. Identify the production requirement that calls for Enterprise, then compare total cost against implementing the same requirement another way. Published Team or Business rates do not price a custom Enterprise contract.
Should a new app start with annual billing?
Estimate how many people will build and use the app before making an annual commitment. If those cohorts are uncertain, compare the flexibility of monthly billing with the discounted annual rates. Include the annual terms for excess usage and changes to the commitment in that decision.
Does a low subscription price mean the app is inexpensive to deliver?
The subscription is one part of the budget. Existing connections and working calculations can reduce the build work, while a new data model or access requirement adds work. Ask for the implementation and ongoing support estimate before deciding what the app will cost.