Deploy

Setup Retool in your own VPC.

Retool can be setup on-prem in 5 minutes.

Why deploy on-prem?

If you're like us, you probably have a lot of data that is only accessible from your private network (locally or behind your VPN). That's why we built the on-prem version of Retool.

This 5 minute guide will help you set up a trial of on-premise Retool locally or on your own cloud infra. This requires command line experience. If you're looking to get started with Retool’s SaaS product without worrying about installing software, go here.

How to deploy?

There are two ways to try Retool on-prem:

1. On-premise trial

  • When to use? If you need > 5 users, or any of the features on our Enterprise plan. Any large production use case or trial requires a license key.
  • How to get started? Book a call to get a license key.

2. Local deployment

  • When to use? If only you will be using the tool to test connecting to data hosted locally. This will be on your machine so you cannot easily share your tool with collaborators/users.
  • How to get started? Follow the local deployment steps here.

🚧

A license key is required for on-premise deployments of greater than 5 users.

Book a call to get a license key.

Deployment options

You can deploy Retool locally or on your own cloud infra using Docker, Kubernetes, Heroku, or Render. If you're not sure what to use, use Docker.

  1. Local deployment
  2. Docker deployment
  3. Kubernetes deployment
  4. Heroku deployment
  5. Render deployment

Updated about a month ago



Deploy


Setup Retool in your own VPC.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.