Retool deployment & regions
★★★★★ 4.7 CE

Retool Deployment, Regions & Data Residency 2026

Retool Cloud is multi-tenant on AWS with no region choice or EU endpoint; residency comes only from self-hosting. It is SOC 2 Type 2 and ISO 27001 certified.

Retool Deployment & Regions verdict

Verified today·7 sources checked

Retool Cloud runs on AWS as multi-tenant, with no region selection and no EU endpoint.

Region control comes only from self-hosting. Retool-managed deploys into your AWS VPC, where you pick the region and it goes live in about 24h via CloudFormation.

How to pick your regions

If you need data residency or a specific region, skip multi-tenant Cloud. Choose Retool-managed, where the VPC is your AWS account, you pick the region and Retool operates it, or self-managed on Kubernetes. Docker is fine for a quick trial but non-production. Wire SSO through OIDC or SAML and source control through GitHub or GitLab. For EU or UK data on Cloud, you are relying on SCCs, so confirm HIPAA directly if you handle PHI.

Honest limits
  • Retool Cloud has no region selection and no EU endpoint, so EU or in-region residency requires self-hosting.
  • Self-hosting is Enterprise-only, and Docker is non-production, so production needs Kubernetes with Helm or Retool-managed. No multi-region failover is published for the multi-tenant Cloud, and there is no contractual SLA.
  • HIPAA is not referenced on public pages, so confirm a BAA directly for PHI, and rely on SCCs for EU or UK Cloud transfers.
Cloud hosting
AWS multi-tenant (no region pick)
EU residency
Self-hosted only
Self-host region
Any AWS region
Deploy
Docker / K8s-Helm / CloudFormation
Compliance
SOC 2 II + ISO 27001 (no HIPAA)
View sources

This page covers where Retool runs and how residency works. Performance and pricing live on their own pages.

Pick your Retool region and deployment

Retool deployment configuration

Deploy a non-production instance on a Linux VM (Ubuntu 22.04+, 64 GiB RAM, 8 vCPU, 60 GiB storage). Add your license key to the env file and start the Docker Compose stack. Docker is for testing only; use Kubernetes for production.

Docker (non-production)bash
git clone https://github.com/tryretool/retool-onpremise
cd retool-onpremise
./install.sh                       # generates docker-compose.yml + env files
echo "LICENSE_KEY=your-license-key" >> docker.env
docker compose up -d               # js-executor, agent-sandbox, r2Agent, rrGitServer, MinIO

Production self-hosting runs on Kubernetes with Helm. The Terraform blueprint provisions the full AWS stack (VPC, EKS, RDS PostgreSQL, S3, ALB, ACM, Route 53). Set the AWS region and Helm chart version, then apply (30 to 45 minutes, mostly EKS and RDS creation).

Kubernetes on AWS (Terraform + Helm)bash
# terraform.tfvars
#   region                    = "us-east-1"   # any AWS region
#   retool_helm_chart_version = "6.11.5"
terraform init
terraform apply        # VPC, EKS, RDS PostgreSQL, S3, ALB, ACM, Route 53
# Pods: retool-api, retool-workflows-worker, retool-code-executor, agent-sandbox-controller

Retool deploys and manages a stable instance inside your own AWS VPC via a one-click CloudFormation template. You select the AWS region at setup; provisioning completes within 24 hours and Retool handles updates and patches (new stable every ~3 months).

Retool-managed (CloudFormation)bash
# Retool-managed: customer-owned VPC on AWS, Retool operates it
# 1. Launch the Retool CloudFormation template (1-click) in your AWS account
# 2. Choose deployment preferences, including the AWS region to deploy in
# 3. Retool provisions an EKS cluster + Amazon RDS for PostgreSQL (~24h)
#    and manages updates and security patches for you

Regions and hosting model

ModelWhere it runsRegion controlNotes
Retool Cloud (multi-tenant)Retool's AWSNone (not disclosed)IPs map to us-west-2 / us-east-1; single unified status
Retool Cloud (single-tenant)Dedicated Retool infraNot publicly disclosedDedicated instance, same AWS backbone
Retool-managed self-hostedYour AWS VPCYou pick the AWS regionEKS + RDS; Retool manages updates; ~24h
Self-managed (Kubernetes)Any cloud / your infraAny regionHelm chart 6.11.5; example region us-east-1
Azure / DockerAzure VM/AKS or Linux VMAny regionAzure containers; Docker non-production
Status reportingSingle unified Cloud statusNo region breakoutStatus page does not split by US/EU cluster

Region reach, deployment targets and identity

CapabilityHow it worksNotes
Region selectionSelf-hosted onlyRetool-managed and self-managed pick the AWS region; Cloud does not
Deployment targetsDocker / K8s / Azure / AWSDocker non-prod; Kubernetes-Helm for production
Multi-region failover (Cloud)Not publishedFault-tolerant AWS, but no multi-region failover detail
SSO / identityOIDC + SAML 2.0Google (LDAP sync), Okta, ADFS, other SAML IdPs
Source control5 providersGitHub, GitLab, AWS CodeCommit, Bitbucket, Azure Repos
Network egress (self-hosted)Retool IPs + domainsLicense/auth: 35.92.202.168/29, 44.211.178.248/29 on 443

Data residency and storage model

DeploymentData residencyData Retool storesNotes
Multi-tenant CloudNo residency controlProxy, no customer dataRetool's AWS; app definitions and audit logs only
Self-hosted, Retool-managedYour AWS regionNo Retool accessCustomer-owned VPC; full residency control
Self-hosted, self-managedAny region / infraNo Retool accessno Retool personnel access to Customer Data
EU residencySelf-hosted onlyCustomer-controlledNo EU-specific Retool Cloud endpoint; EU residency needs self-hosting
International transfersSCCs (EU/UK)Per modelStandard Contractual Clauses; DPO [email protected]
ComplianceSOC 2 II, ISO 27001, GDPR, CCPAn/aHIPAA not found on public pages

What to verify before you commit to Retool

  • Retool Cloud is multi-tenant on AWS with no region selection and no EU-specific endpoint, so EU or in-region data residency requires self-hosting (Retool-managed or self-managed), not Cloud
  • There is no published multi-region failover architecture for the multi-tenant Cloud and no contractual SLA, only fault-tolerant AWS and status-page actuals, so weigh that against your availability needs
  • Self-hosting is an Enterprise feature and Docker is non-production only; production requires Kubernetes with Helm (EKS, 30 to 45 minute Terraform apply), so budget the operational overhead or choose Retool-managed
  • HIPAA is not referenced on public pages (SOC 2 Type 2 and ISO 27001 are), so confirm a BAA directly if you handle PHI, and use SCCs for EU/UK transfers on Cloud

Retool Deployment & Regions FAQ

Where is Retool hosted and can I pick a region?

Retool Cloud runs on Amazon Web Services as a multi-tenant platform, and you cannot pick the region. The specific AWS regions are not disclosed, though license IPs map to us-west-2 and us-east-1. Region control comes only from self-hosting: Retool-managed lets you choose the AWS region for a Retool-operated VPC, and self-managed Kubernetes runs in any region or infrastructure.

Does Retool support EU data residency?

Not on Cloud. There is no EU-specific Retool Cloud endpoint, so EU or in-region residency requires self-hosting, either Retool-managed in your AWS VPC in an EU region, or self-managed on your own infrastructure. For EU or UK personal data on Cloud, Retool uses Standard Contractual Clauses, with a DPO at [email protected], but the data still resides in Retool's AWS.

How do I self-host Retool?

Three production-relevant paths. Docker on a Linux VM, 64 GiB and 8 vCPU minimum, is for non-production. Production runs on Kubernetes with Helm. A Terraform blueprint provisions the full AWS stack, from VPC and EKS to RDS PostgreSQL, S3, ALB, ACM, Route 53, in 30 to 45 minutes. Retool-managed instead deploys the same stack into your AWS VPC via a one-click CloudFormation template, ready in about 24h with Retool operating it. Self-hosting is an Enterprise feature.

Does Retool store my data?

For external data sources, no. Retool is a query proxy that forwards requests to your database and does not store customer data, only app definitions, permissions, audit logs, workflow state, with optional short-lived caching you control. On self-hosted deployments, no Retool systems store customer data and no Retool personnel can access it. Backups, where Retool does store data, are nightly with 7-day retention, redundant across data centers.

Does Retool have multi-region failover or an SLA?

Retool Cloud runs on fault-tolerant AWS infrastructure built to survive individual server or data-center failures, but no multi-region failover is published for the multi-tenant platform, and there is no contractual SLA percentage. The status page reports 90-day actuals instead, with the web app at 99.05% and workflows at 99.97%. For stronger availability control, self-host and design your own resilience.

What compliance certifications does Retool hold?

Retool holds SOC 2 Type 2 and ISO/IEC 27001:2022, both with documents in the trust center, plus an independent pentest report. It is GDPR and CCPA compliant, using SCCs for EU or UK transfers. HIPAA is not referenced on public pages, so confirm a BAA directly if you handle protected health information. Self-hosting is the common path for regulated workloads, since no customer data leaves your VPC.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources
SourceWhat was checkedLast checked
Retool OfficialOfficial product pageJuly 10, 2026
Retool Developer docsSecurity and complianceJuly 10, 2026
Retool Developer docsRetool Managed QuickstartJuly 10, 2026
Retool Developer docsTutorials KubernetesJuly 10, 2026
Retool Developer docsTutorials DockerJuly 10, 2026
Retool Developer docsPrivacy PolicyJuly 10, 2026
Retool Govern Enterprise Apps Self HostedGovern Enterprise Apps Self HostedJuly 10, 2026

Every fact on this Retool page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.