Deploying 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 self-host Retool so they remain compliant.
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).
- Use Retool with other on-premise infrastructure like Git or single sign-on (SSO).
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.
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:
Updated about 1 month ago