Deploying on multiple AWS accounts using the Business Plan

💬 Self Hosted Retool
1

Can I deploy Retool on multiple AWS accounts on the Business Plan?

I know I won't have Source control access but if I deploy it using the same key what would happen then? Will it fail?

If it doesnt fail, how does Retool treat the different enviroments?

2

Hello @Joseph_Fidanque,

If you are using Retool on the Business Plan, you can set up different environments (like Development, Staging, and Production) inside one Retool instance using the Environments feature. This lets you manage different API keys, databases, and settings for each stage without needing multiple deployments.

:point_right: Learn more about Configuring Resource Environments: Retool Environments Guide

Now, if you try to install Retool on multiple AWS accounts using the same license key, here’s what you should know:

1. Will it fail?

  • Probably not right away. Retool may not immediately block it, but their licensing rules might not allow multiple deployments under one key.

2. How does Retool handle different environments?

  • If you deploy multiple separate instances, they will not sync with each other. Each one will be like a completely different Retool setup.
  • The better way to handle different environments is to use Retool’s built-in Environments feature in one deployment.

:point_right: Learn more about Multi-instance Deployment: Retool Multi-instance Deployment Guide

3. What’s the best approach?

  • If you just need separate environments (Dev, Staging, Prod), use the built-in Environments feature—this is the easiest way.
  • If you really need completely separate setups (like different AWS accounts for different teams), check with Retool’s support to make sure your license allows it.

Hope this helps!

2 Likes
3

Thanks for reaching out, @Joseph_Fidanque!

Multi-instance deployments are currently scoped to organizations on a Committed plan, which typically means Enterprise. Although we technically don't enforce this up front, deploying multiple instances with a self-serve license key can cause billing issues down the road. We will eventually build out functionality to prevent it in the first place. :+1: