Skip to main content

Requirements for Self-hosted Deployments

Applicable to customers on any plan.

These Requirements for Self-Hosted Deployments (“Requirements”) apply to customers who host the Retool Platform on their own infrastructure (a “Self-Hosted Deployment”) and supplement and form part of the Agreement between Retool, Inc. (“Retool”) and Customer. "Agreement" means the Retool Master Subscription Agreement or other written agreement between Retool and Customer, as specified in the Customer's then-current Order Form, that governs Customer's use of the Retool Platform.

Capitalized terms used but not otherwise defined in these Requirements will have the meanings given to them in the Agreement. As used in these Requirements, "Retool Platform" will also mean the "Services" or other similar term used in the Agreement to refer to Retool's developer tools and platform.

A. For All Self-Hosted Deployments​

1. License Grant​

Subject to the Agreement, Retool grants to Customer a non-sublicensable, non-transferrable, and non-exclusive license, during the subscription term of the current Order Form, to install, operate and use the Retool Platform on Customer’s own infrastructure, in accordance with the Documentation and the authorized scope of use for the Retool Platform as specified in the current Order Form (“Scope of Use”).

2. License Verification​

Customer will (a) permit Retool to verify Customer’s compliance with the Scope of Use; or (b) upon Retool’s request, provide written verification to Retool that demonstrates such compliance. Such written verification will be in the form of a report generated by the Self-Hosted Deployment or other form that is reasonably necessary for Retool to verify Customer’s compliance. Unless otherwise specified in the applicable Order Form, if Customer has exceeded its Scope of Use and, upon Retool’s request, does not use good-faith efforts to resolve or address such excess use with Retool, Retool may invoice Customer the fees applicable to such use. Customer will pay any amounts invoiced by Retool under this section in accordance with the payment terms in the Agreement.

3. Usage Information​

Retool may collect and use Usage Information as permitted under the Agreement.

4. New Releases​

Retool makes new releases of the Retool Platform for Self-Hosted Deployments available as described in the Documentation. It will be Customer’s responsibility to install the most current “Stable” release and all maintenance releases as soon as reasonably practicable once available. Once a release is considered as deprecated, as described in the Documentation, Customer acknowledges and agrees that such deprecated release will no longer be supported by Retool and Retool will no longer provide bug fixes, security patches and updates, or any other maintenance. Retool provides no warranties or guarantees regarding the performance, security, or stability of deprecated releases of the Retool Platform and disclaims all liability for any issues that may arise as a result.

B. For Self-Hosted Deployments (Retool-Managed)​

Only applicable if Customer’s then-current Order Form includes a subscription for a “Self-Hosted – Retool-Managed Deployment.”

1. Definitions​

  • “Retool-Managed Deployment Services” means Retool’s offering for deploying the Retool Platform in the Customer Cloud Account, including provisioning the Services Infrastructure and maintaining and monitoring the Services Infrastructure through the Runner VM.
  • “Customer Cloud Account” means Customer’s account with Amazon Web Services, or any other cloud hosting provider approved by Retool in the applicable Documentation, that is dedicated for the Retool Platform.
  • “Runner VM” means the Retool-managed automation tooling, deployed in the Customer Cloud Account, that communicates with Retool’s control plane to perform limited automated operational tasks with respect to the Services Infrastructure.
  • “Services Infrastructure” means the Retool-managed components of the infrastructure, as set forth in the applicable Documentation, that are required to support operation of the Retool Platform and have been configured by Retool based on Customer’s instructions. For the purposes of these Requirements, the term “Services Infrastructure” will exclude the Retool Platform.

2. Documentation​

2.1. Documentation for the Retool-Managed Deployment Services is available at https://docs.retool.com/self-hosted/retool-managed/.

3. Customer Responsibilities​

3.1. In order for Retool to provide the Retool-Managed Deployment Services, Customer must (A) at its sole cost and expense, create and maintain a Customer Cloud Account during the term of the applicable Order Form and (B) provide information reasonably requested by Retool in a timely manner. Customer will follow all other set-up requirements and instructions provided in the applicable Documentation or communicated by Retool (including via email). Retool will not be responsible for any delays or interruptions in Customer’s use of the Retool Platform to the extent caused by Customer’s failure or delay in meeting the requirements in this section.

3.2. Customer acknowledges and agrees that the Retool-Managed Deployment Services require a division of roles and responsibilities, as described in the applicable Documentation. Customer will not, nor will it permit an Authorized User or any third party to, modify, delete, or interfere with the Services Infrastructure or the Runner VM. Retool will not be responsible for any performance or functionality issues that result from Customer, an Authorized User, or any third party’s modification, deletion, or interference with the Services Infrastructure or Runner VM.

3.3. Customer is solely responsible for (i) implementing and maintaining industry standard controls and measures to secure access, and prevent unauthorized access to, the Customer Cloud Account; (ii) the handling of encryption keys managed by Customer for the Retool-managed deployment; and (iii) ensuring that Retool does not have access to resources, Databases, and Customer Data if access is not necessary for Retool to provide the Retool-Managed Deployment Services.

4. Retool Responsibilities​

4.1. Subject to Customer’s compliance with these Requirements and the Agreement, Retool will perform the Retool-Managed Deployment Services, during the term of the then-current Order Form and in accordance with the applicable Documentation. Retool’s obligations and responsibilities with respect to the Retool Platform are set forth in the Agreement.

5. Termination​

5.1. If Customer’s subscription to the Retool-Managed Deployment Services under the applicable Order Form terminates or expires and Customer has not executed a new Order Form to continue using the Retool Platform under a different deployment model, Retool may limit, suspend, or terminate Customer’s ability to access and use the Retool Platform as deployed in the Customer Cloud Account.

5.2. If Customer’s subscription to the Retool-Managed Deployment Services under the then-current Order Form terminates or expires, but Customer has executed a new Order Form to immediately continue using the Retool Platform under a different deployment model, Customer will comply with instructions provided by Retool to facilitate the migration of the Retool Platform to the new deployment model agreed upon by the parties in the Order Form.