Licensing and deployment options for building client apps in Retool

💬 App Building
1

Hello Retool Team, I’m an IT Specialist and I recently built a complete web application using Retool AI for a commercial client. The application is designed for a retail store and includes: * Point of Sale (POS) * Inventory and stock management * 3 separate warehouses * Delivery management * Store operations and reporting I originally built the application using a free Retool account with Google login, and I have now reached the AI credit limit. Before upgrading, I would like to clarify the best licensing and deployment option because this is a commercial project that I plan to deliver to my client. My main questions are:

  1. Can I upgrade my current Retool account and legally use the application commercially for my client?
  2. Can I transfer the complete application to a separate Retool account owned by my client, so the client becomes the owner of the application and its data?
  3. Is there a way to export or deploy the application as a standalone/local application that can be installed on the computers at the client’s store and warehouses, without depending on Retool Cloud?
  4. If local/self-hosted deployment is possible, which Retool plan would I need, and what would the licensing cost be?
  5. I also noticed that Retool has an Agency program for developers building applications for clients. Would my use case qualify for the Agency program, and would it allow me to develop and commercially deliver this application to my client?
    I am happy to pay for the appropriate plan. I just want to make sure I choose the correct plan and deployment model before upgrading.
    Thank you for your help
2

Summary

An IT specialist built a complete commercial retail app (POS, inventory across 3 warehouses, delivery, reporting) using Retool AI on a free account, hit the AI credit limit, and wants to know the correct licensing/deployment path before upgrading — including commercial use rights, transferring ownership to the client, standalone/offline deployment, self-hosted plan requirements, and whether an Agency program applies.

AI Response

Retool apps can be built and used commercially on a paid plan, but they must always run inside the Retool environment — there is no way to export an app as a fully standalone/offline program that installs directly on store or warehouse computers with no Retool dependency. To hand the project to the client, the recommended approach is to export the app and import it into a Retool org owned by the client, so the client becomes the owner of the app and its data (users still log in to Retool to use it). A practical tip from the community is to save the final build as the app's live version so it displays correctly regardless of which plan the client's org is on. Self-hosting is possible but is an Enterprise-tier offering that requires a license key obtained from a Retool account manager, and even self-hosted deployments still connect to Retool's licensing service, so it is not a truly offline/local install. Because commercial-use terms and any Agency/partner program eligibility are governed by Retool's pricing and Terms of Service rather than by product docs, those specifics should be confirmed directly against Retool's official pricing and legal pages before upgrading.

Sources

:bookmark: Building and Shipping Apps for Clients and Ownership Options
A solved thread on the identical scenario, confirming apps must run in the Retool environment, that ownership is transferred by exporting/importing into the client's own org, and advising to set the final release as the live version regardless of the client's plan.
:bookmark: Deploy self-hosted Retool with Docker | Retool Docs
Documents the self-hosted deployment path, showing it requires a Retool license key (an Enterprise offering obtained via an account manager) and that Docker is non-production only, clarifying that self-hosting is not a fully offline standalone install.

The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a :heart:, :+1:, or :-1:. Or by marking this post as the "Solution"! Let us know if you have any feedback here. :rocket: