Outbound Static IPs
When an API, database, payment provider, or customer firewall accepts traffic only from approved source IPs, route those connections through QuotaGuard. Your application keeps its current hosting platform while QuotaGuard operates the stable outbound network identity, availability, monitoring, failover, maintenance, and support.
Is This Your Requirement?
This architecture solves a specific problem: the receiving system will not accept your application until its source network addresses are approved.
Need customers or partners to reach your application through fixed destination IPs? See Inbound Static IPs →
How It Works
Configure the calls that need fixed source IPs to use QuotaGuard. The protected destination sees one of the two addresses assigned to your subscription.
Official Platform Documentation
Render's official documentation explains how services can send outbound traffic through QuotaGuard's load-balanced pair of static IPs to systems outside Render that use IP allowlists.
Read Render's QuotaGuard Documentation →Implementation
Static is the standard starting point. Choose Shield when policy requires a TLS-protected connection from your application to the proxy.
Get the proxy URL and both assigned static IP addresses from your QuotaGuard dashboard.
Use a proxy-aware HTTP client, SOCKS5, or QGTunnel based on the protocol and application.
Give both addresses to the receiving team, verify the observed source IP, and test failover before production.
Test the real connection path. Confirm that the exact SDK, database driver, or command used in production honors the proxy configuration. Test representative latency, authentication, and failover behavior against the actual destination.
Managed Infrastructure
The static address is only one part of the service. QuotaGuard operates the production network path behind it.
Choose the Right Architecture
All three options give approved outbound connections a predictable network identity. The difference is the connection to the proxy and whether the infrastructure is shared or customer-only.
APIs, automations, databases, payment providers, and customer firewalls
Remains encrypted to the destination and is not decrypted by QuotaGuard
Standard HTTP or SOCKS5 proxy protocol
Stable IP pair on managed shared infrastructure
$19 starting monthly price
Start Static TrialSecurity reviews and approved compliance-sensitive architectures
Remains encrypted to the destination and is not decrypted by QuotaGuard
TLS-protected HTTP proxy or SOCKS5 over TLS
Stable IP pair on managed shared infrastructure
$29 starting monthly price
Start Shield TrialContracts, security reviews, or architectures requiring customer-only IPs and proxy resources
Available with Static or Shield connection architecture
Dedicated IP addresses and proxy resources reserved for your organization
Static Enterprise from $219/month
Shield Enterprise from $269/month
Technical Boundaries
A useful architecture is explicit about the connection path, protocol, and controls that remain outside the proxy.
QuotaGuard typically adds only a few milliseconds of latency. Choose from 12 global regions to place the proxy close to your application, then test representative traffic against the actual destination.
Your client or library must actually use the proxy. Some SDKs ignore standard proxy environment variables.
Database and other raw TCP connections generally require SOCKS5 or QGTunnel instead of an HTTP proxy.
Only connections configured for QuotaGuard use its static IPs. Other traffic keeps its normal route.
Allowlist both dashboard-assigned addresses so failover does not interrupt the integration.
Standard plan IPs are stable but shared. Use Enterprise when customer-only addresses are required.
Traffic opened entirely inside a vendor-hosted service cannot use your QuotaGuard route unless you control a proxy-capable component in the path.
Static source IPs do not replace TLS, credentials, authorization, rate limits, logging, or monitoring.
Keep your current application and hosting platform. Route the connections that need fixed source IPs through infrastructure QuotaGuard operates for you.
Need help choosing HTTP proxy, SOCKS5, QGTunnel, Shield, or dedicated infrastructure? QuotaGuard engineering can review the connection path with you.
Outbound Static IP FAQ
It is a stable public source address used when your application connects to another system. The receiving API, database, or firewall can allowlist that address and recognize traffic coming through the approved route.
Yes. Outbound static IPs identify your application when it connects to another system. Inbound static IPs give customers and partners a fixed destination for reaching your application.
The pair supports availability and failover. The receiving system should allowlist both dashboard-assigned addresses so traffic can continue through either healthy route.
No. Only the connections configured to use the proxy travel through QuotaGuard. This lets you route calls that need stable source IPs while leaving unrelated traffic on its normal path.
No. With both Static and Shield, outbound HTTPS remains encrypted to the destination and QuotaGuard does not decrypt the application payload.
Static uses the standard HTTP proxy protocol or SOCKS5 for the application-to-proxy connection. Shield adds TLS protection to that connection. With either product, the outbound HTTPS payload remains encrypted to its destination.
Yes, when the application and destination are compatible with the supported connection method. SOCKS5 and QGTunnel cover many database and non-HTTP TCP connections. Confirm the exact protocol and client behavior before production.
Send a request through the configured proxy to ip.quotaguard.com and compare the observed source address with the pair shown in your dashboard. Then test the actual production destination.
No. Standard subscriptions receive a stable IP pair on managed shared infrastructure. Enterprise plans provide customer-only IP addresses and dedicated proxy resources.
Yes, but typically only a few milliseconds. QuotaGuard operates across 12 global regions, so you can place the proxy close to your application and keep the additional network distance minimal. Test representative requests against the real destination before production.
No. Keep TLS, application credentials, authorization, rate limits, logs, and monitoring. Source-IP allowlisting adds a network control; it does not replace application security.
For over a decade, QuotaGuard has provided reliable, high-performance static IP and proxy solutions for cloud environments like Heroku, Kubernetes, and AWS.
Get the fixed identity and security your application needs today.
