Hello,
We’re running Retool selfhosted (Enterprise) for over 2.5 years now and I’m curious how other companies/user have setup their selfhosted Retool instance.
There are many options to deploy Retool selfhosted and some are easier to achieve than others, while some might scale/perform better.
We’re currently hosting our instance on a Azure VM with Docker and although this is relatively simple to maintain, I’m looking into more robust and future proof solutions that scale better and have proper develop/test/production instances with source control.
We’re currently running Retool Selfhosted 3.284.5 on an Azure VM (4 vcpu and 16GB RAM Ubuntu 22.4 LTS) and have put all (Retool) databases on an external Azure Postgres Flexible server.
This is working fine for our 40 users, but currently the load is not that high as not all 40 users are all using Retool at the same time. We’re running about 20 different apps and 10 workflows (some during the night, some every 10 mins througout the day).
Retool is accessible from the internet, therefor we’ve deployed a Fortinet WAF, limiting incoming connections to certain countries where our offices are located. This is working for now and doesn’t cost much, but management can be difficult somethimes due to a lack of options in teh WAF config.
Retool login is being handled by Azure Entra ID SSO with Conditional Access policies in place which limits access only to compliant devices.
For the future I might be looking at a K8’s solution, but personnaly I don’t have a lot of experience with K8.
So please share how you’ve setup your instance and maybe why you choose for the setup.
How are you hosting and securing Retool selfhosted?
BR. Marc