Skip to main content

Self-hosted deployments

Choose between a Retool-managed or self-managed self-hosted Retool instance.

Self-hosted Retool instances are available on an Enterprise plan only.

A single-tenant instance is deployed on its own dedicated infrastructure that is not shared with any other instance. Self-hosted instances run on your own infrastructure. You can also choose to have Retool deploy and manage this instance for you.

OptionManaged byUse caseOperational overhead
Retool-managedRetoolOrganizations that need data residency or infrastructure control without managing Retool.Low
Self-managedYouOrganizations in regulated industries that need full control over a single-tenant deployment.High

Self-hosted, Retool-managed​

A self-hosted, Retool-managed deployment is a single-tenant instance with low operational overhead. Retool deploys a stable release instance on AWS and manages it for you, providing you with a self-hosted deployment that's managed by Retool. As this is on your AWS infrastructure, you retain full ownership of, and control over, your data, encryption keys, and access.

Retool securely manages the instance for you, such as performing updates. There is some operational overhead involved as you maintain the AWS infrastructure on which the instance is deployed.

Self-hosted, self-managed​

A self-hosted, self-managed deployment is a single-tenant instance that you host, deploy, and manage. This option provides you with complete control and ownership but with the highest operational overhead compared to others. You are responsible for all of the operational overhead of maintenance, such as updates.

Retool is not involved in the hosting, deployment, or management of this instance type. You deploy self-hosted Retool for use in production on a Kubernetes cluster using Helm. For testing purposes, you also have the option to deploy locally to a Linux-based VM using Docker.