Retool Self-Hosted, Self-Managed
Commercial single-tenant Retool deployment installed and operated on customer-managed Kubernetes infrastructure.
6 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster
Runs in
Documented customer environment
Distributed Retool containers on Kubernetes with external PostgreSQL, object storage, ingress and optional Temporal services
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages Kubernetes, PostgreSQL, object storage, DNS, TLS, secrets, networking, backups, capacity, upgrades and the Retool license.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Official Retool Terraform and Helm deployment paths ↗ · Source checked 2026-11-16
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Official Retool Terraform and Helm deployment paths ↗ · Source checked 2026-11-16
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Official Retool Terraform and Helm deployment paths ↗ · Source checked 2026-11-16
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Official Terraform blueprints for Amazon EKS, Azure AKS or Google GKE, or Helm into an existing supported Kubernetes cluster |
|---|---|
| Infrastructure | Servers / containers Production deployments run persistent Retool services on customer EKS, AKS or GKE infrastructure with external database and object-storage dependencies. |
| Licensing model | Commercial Only Current pricing places self-hosted and air-gapped deployments in Enterprise with custom annual pricing. Product-specific subscription and license-key terms apply; cloud per-seat prices do not price this deployment. |
| License | Commercial Enterprise subscription with custom annual pricing and a self-hosted license key. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
11 of 12 fields researched (92%) · 10 documented · 1 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery
Retool’s AWS Marketplace listing explicitly describes self-hosted and Retool-managed AWS environments, with private-contract procurement. AWS classifies delivery as a SaaS contract; confirm the self-managed Enterprise entitlement rather than assuming an AMI installer or included infrastructure. Retool also announces Google Cloud private-offer purchasing with the same deployment options; the exact offer and agreement must match the self-hosted subscription.
Vendor-published AWS offer; procurement and application hosting are distinct · Source ↗ · Google Cloud Marketplace procurement and commitment conditions ↗ · Offer prodview-cqgbgmrm63i4y ↗ — Retool; SaaS contract/private offer; select self-managed Enterprise entitlement · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- Cloud commitment eligibility
Edition-dependentEvidence and scope for Cloud commitment eligibility
Retool states that eligible Google Cloud Marketplace purchases can draw down a Google Cloud commitment and that Marketplace procurement preserves deployment options. Purchases use a private offer; the amount credited depends on the buyer’s Google agreement and accepted offer. This is not a blanket credit promise for all purchases or providers.
Google Cloud private-offer procurement; buyer agreement controls eligibility · Source ↗ · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
Retool documents SAML and OIDC providers, including Entra ID and Okta, plus identity-provider group/role mapping. Apply the self-hosted instance configuration and subscription entitlements; Google Group sync is a separate integration.
Retool organization SSO; protocol support does not establish every plan entitlement; current pricing includes this capability in Enterprise · Source ↗ · Enterprise entitlement matrix ↗ · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning
SCIM provisioning is documented for self-hosted versions 2.32.1+, with bearer-token authentication and /api/scim/v2/* endpoints. The guide covers Okta and Entra ID; the identity provider must reach the instance through its firewall.
Self-hosted technical configuration; selected subscription governs commercial entitlement; current pricing includes this capability in Enterprise · Source ↗ · Enterprise entitlement matrix ↗ · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
Retool’s legal security practices describe independent SOC 2/ISO audits and direct readers to its Trust Center. Those public practices alone do not establish report dates or coverage of the customer-operated self-managed environment.
Vendor controls and audit availability; customer-environment scope/period needs the actual report · Source ↗ · Reviewed 2026-11-16
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The code-executor uses nsjail, which needs privileged container access. The documented fallback runs code without sandboxing if that access is unavailable. Review this specific container’s isolation separately from agent and JavaScript executors.
Self-managed code-executor container; not an attestation for every Retool service · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation
Retool’s current Enterprise pricing explicitly offers air-gapped deployments. The standard self-managed guide still requires outbound license/authentication/usage services, so obtain the separate air-gap license, artifacts and procedure from Retool rather than applying the standard online setup unchanged.
Enterprise commercial air-gap option is confirmed; deployment-specific procedure and integration dependencies require account-team coordination · Source ↗ · Standard deployment outbound requirements ↗ · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Retool provides Terraform blueprints that provision EKS, AKS or GKE and deploy Helm. Kubernetes with Helm is the production path for 4.0 and later; Compose is for development and proofs of concept. AWS agent sandboxes require EC2-backed EKS workers rather than Fargate.
Self-managed Retool 4.0+; select matching chart and application versions · Source ↗ · Deployment artifact ↗ (main (moving branch)) · Reviewed 2026-11-16
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The current Helm guide calls for at least 32 CPU cores and 64 GiB available across the workload-node pool. Agent sandbox pods scale with builder sessions; the external PostgreSQL database, storage and peak autoscaling capacity must also be planned.
Current production Helm stack with app-builder/agent services; not the older Compose baseline · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Current pricing places self-hosted and air-gapped deployment in Enterprise, with custom annual pricing. Its published cloud per-seat prices do not price a self-hosted Enterprise installation. The subscription and license-key terms govern use.
Self-hosted Enterprise procurement; excludes cloud infrastructure and operating labor · Source ↗ · Self-hosted legal terms ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed vendor release is 4.86.0, published 2026-11-11. This is a dated, scoped snapshot; it does not establish compatibility with another chart, cloud package or commercial edition. Retool documents quarterly stable releases and six months of support for each stable version.
Self-hosted stable-channel release, separate from cloud/edge versions; source supplies a publication day, not a timestamp · Source ↗ · Reviewed 2026-11-16
Documented · Editor reviewed.
Show all fields (1 not researched)
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry covers self-hosted, self-managed Retool, not Retool-managed hosting. Kubernetes with Helm is the supported production path for Retool 4.0 and later; Docker Compose is non-production only. EKS must use EC2-backed workers rather than Fargate for the agent sandbox. The standard deployment requires outbound access for license checks, authentication and usage reporting; Enterprise pricing separately offers air-gapped deployment, requiring the appropriate license and vendor-provided procedure. Workflows and Agents require Temporal, and Retool recommends its managed Temporal Cloud service unless the customer operates a compatible cluster.
Category fit
- Internal tools
- Provides a self-hosted low-code platform for building internal applications and operational interfaces.
- Workflow automation
- Runs Retool Workflows and related automation services inside the customer-operated deployment.
Compare within Internal tools
- Appsmith Self-HostedBuild internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
- Azure
- Budibase Self-HostedBuild operational apps and automations on customer-hosted infrastructure.
- DigitalOcean
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
- AWS
- Azure
- Mendix on KubernetesCommercial low-code application runtime operated in customer Kubernetes infrastructure.
- AWS
- Azure
- Google Cloud
- STACKIT
Showing 8 of 10 other listings in Internal tools. These products address related workflows; read their category-fit notes before comparing scope. See all of Internal tools →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Self-hosted, self-managed Retool ↗docs.retool.com
- Self-managed Retool quickstart ↗docs.retool.com
- Retool Kubernetes deployment tutorials ↗docs.retool.com
- Deploy Retool on Kubernetes with Helm ↗docs.retool.com
- Retool product-specific terms ↗docs.retool.com
- Enterprise deployment options and pricing ↗retool.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Official Retool Terraform and Helm deployment paths ↗ · AWS, Azure, Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.
Retool provides production Terraform blueprints for AWS, Azure and Google Cloud and explicitly targets Amazon EKS, Azure AKS and Google GKE. Customers may alternatively deploy with Helm into an existing supported cluster.
- Official Retool Terraform and Helm deployment paths ↗ · AWS, Azure, Google Cloud
- Infrastructure evidenceChecked
- Licensing evidenceChecked