Static Inbound & Outbound Static IPs for Render Applications

No.

You can use QuotaGuard with standard Web Services, Background Workers, and Cron Jobs.

It works across all Render service types.

Yes.

By using our SOCKS5 proxy, you can securely tunnel from Render to MongoDB Atlas, allowing you to whitelist our static IP in Atlas's "Network Access" list.

You can define the QUOTAGUARDSTATIC_URL or QUOTAGUARDSHIELD_URLas an environment variable in your render.yaml file.

We recommend storing the actual connection string in a Render Secret Group and referencing it in the Blueprint for security.

Absolutely.

Since the proxy configuration is an environment variable, every new instance Render spins up during a deploy will immediately have access to the static IP, ensuring no dropped connections during the transition.

No, we run on high-availability AWS infrastructure.

However, because Render also utilizes AWS (and GCP) under the hood, connection speeds are extremely fast when you match your QuotaGuard region to your Render region.

That is exactly what QuotaGuard solves.

Render keeps large blocks of IPs and they change instance IP blocks frequently.

Your app connects to us (the constant IP), and we connect to your target. Your target sees only our static IP, never the changing Render IP.

We highly recommend it, most of our engineering teams practice this security measure to protect their production IP identification to outside parties.

Using separate QuotaGuard subscriptions (or users) for Dev and Prod ensures that testing data never accidentally pollutes your production databases or API logs.

Please Contact Us if you need help with setting up one paying subscription with both production, staging, and development environments.