Retool Seat True-ups, Usage & Actual Costs: 2026 Guide

Retool bills per builder seat, with a free tier for up to 5 users. Team is $12 per builder a month, or $10 on annual billing, and Business is $65, or $50 annual. So a five-builder team on Team is $60 a month, or $50 annual, before usage. The important detail is that anyone who edits an app becomes a full builder automatically, so the seat count trues up over time. External users, agent hours past the free 20, and AI credit overflow all bill on top. A real Retool cost is therefore builders plus viewers plus usage, not the headline seat rate alone.

A builder seat is a full, paid seat for anyone who creates or edits apps and workflows, priced at $12 on Team or $65 on Business. It is assigned automatically. If a user edits an app or a workflow during a billing cycle, they are upgraded to a builder for that cycle, whether or not you intended it. View-only internal users, who only use the tools others build, bill at $5 on Team and $15 on Business. This auto-upgrade is the most common reason a Retool bill rises unexpectedly. A casual edit turns a $5 viewer into a $12 builder, so it pays to control who has edit access.

Yes, and it is genuinely usable for a small team. The Free plan covers up to 5 users, unlimited web and mobile apps, 500 workflow runs a month, and 5 GB each of database and file storage. For prototyping internal tools or running a small team's apps it is real capacity, not a demo. The limits that bite are the 5-user cap and the 500 workflow-run ceiling. When you need more builders, staging and production environments, or higher workflow limits, Team at $12 a builder is the step up. Use Free to validate that Retool fits your internal-tools workflow before you pay for seats.

External users, people outside your organisation who use apps you build, are billed on the Business plan by tier. They are free up to 50, then $8 each for 51 to 250, $6 for 251 to 500, and $4 above 500, all on annual billing. So an app serving 200 external users is roughly $1,200 a month in external seats on top of your builder seats. That makes external-facing apps a distinct cost line from your internal team's seats. If you plan to serve many outside users, price the tiers before you build, since the external-seat cost can quickly exceed the builder seats it runs alongside.

Both are metered separately from seats. Retool Agents include only about 20 agent-hours a month free; past that, they bill hourly at a model-dependent rate, and execution pauses when the free hours run out. AI credits renew monthly and do not roll over, so any overflow means buying credit packs on paid plans. Workflow runs also cap, at 500 on Free and 5,000 on Team and Business, so an automation-heavy build can hit the ceiling and need Enterprise for headroom. If you lean on AI or agents, model that usage before committing, because it adds a real cost with no relationship to how many builder seats you hold.

It depends on what you need from it. Business at $65 a builder, or $50 annual, buys audit logging, richer permission controls, portals and embedded apps, unlimited resource environments, and access to external users. For a team that needs governance, external-facing tools or fine-grained permissions, that step from the $12 Team seat is justified. For a small internal team that just wants to build apps, Team covers most needs and Business is a large premium. The honest question is whether the compliance, permissions and external-user features are hard requirements. The per-seat jump is more than fivefold, and only pays off when those capabilities are genuinely used.

Yes, at Enterprise. The quote covers seat rates, external-user tiers, SSO, self-hosting and usage, all negotiable for a large account. Anchor with a self-host comparison or a rival figure and committed builder and external counts, and aim near quarter-end. Business also has some room on a large deployment, mainly around seat rates and external tiers. On Free and Team there is nothing to negotiate, since the plan and seat rates are set. The saving there is seat discipline, keeping builders and viewers separate, and annual billing, so for a small team the lever is how you assign seats.

Keep builders and viewers separate, since only people who edit apps need a full seat and editing auto-upgrades a user to a builder. Audit seats before each renewal, take annual billing once the builder count is stable, and control edit access so casual users stay viewers. Model agent hours and AI credit usage before leaning on them, since both bill beyond seats and credits do not roll over. Price the external-user tiers before serving many outside users. For a large deployment, negotiate at Business or Enterprise. Stacked together, those habits hold a Retool bill near the builders and usage you genuinely have.