Self-hosted Retool

Learn about deploying Retool on your own infrastructure.

Deploying Self-hosted Retool on your own infrastructure—such as on-premises—let's you build applications with data in your virtual private cloud (VPC) or behind your virtual private network (VPN). Businesses in the healthcare and finance industries often deploy Retool so they remain compliant.

If you're evaluating a large production use case or need any of our Enterprise plan features, please book a call.

Differences between Cloud and Self-hosted

When you use Retool in our cloud, we manage configuration, updates, and versioning. When you self-host Retool, you manage the infrastructure, configure logging, data access, versioning, etc.

Self-hosted Retool is often used by companies that need to:

  • Store or work with personal identifiable information (PII).
  • Remain compliant with the Health Insurance Portability and Accountability Act (HIPAA). See the Security page for more information regarding HIPAA compliance.
  • Use Retool with other on-premise infrastructure like Git or single sign-on (SSO).

Self-hosted releases

Self-hosted releases are different from Retool's cloud releases, and when you self-host, your version isn't automatically updated. If you decide to self-host, you can read more about updating and release versions.

Getting started

You can deploy Retool locally and on several cloud infrastructure providers like AWS, Azure, Heroku, etc. See our GitHub repository for a full list of options and installation instructions.

Regardless of the option you choose, there are a few high-level steps required to self-host Retool:

  1. Sign up for self-hosted Retool.
  2. Pick a version.
  3. Deploy Retool.
  4. Test your installation.
  5. Keep Retool up to date.