We set up a self-hosted instance but found it was more than we trusted ourselves to properly and securely setup and maintain. At the same time, our IT leaders hate letting traffic from external sites pass through our firewall. Thus, I'm a +1 (please) for ability to restrict IPs. Thx
+1
Having a “network policy” available would be a keen option to have. Yes, Retool is in the cloud and in many instances you want users to be able to get to it from wherever…
In other cases, adding the security of an IP address restriction could make the IT wonks happy.
For now, we are having to configure identity providers with extra bells and whistles…
The self-hosting suggestion doesn't fully solve this for us. We don't have the resources to securely maintain a self-hosted setup long term, and our IT team still isn't comfortable with external traffic through the firewall either way. A native IP allowlist at the org or workspace level would solve this without needing to leave the cloud version.
Hi @trillich / @Furqan_Ashraf !
Thanks for sharing your interest with us! Unfortunately, IP allowlisting is still not supported in Retool Cloud at the moment 
. We have an open feature request for this and I have logged your requests internally.
IP allowlisting is currently available only on Enterprise self-hosted plans, but I understand that switching to this may not be an option for you now for various reasons.
Retool is still actively thinking about ways to add more default security features so while it is not available now, I have passed along your feedback for future consideration to add to the product.
Let me know if you have other questions. We will share more updates here as soon as we get them!
-Jen