

Replit
QuotaGuard gives your Replit app two fixed static IPs and sits at the connectivity layer, so every outbound call leaves from an address your destinations already trust. You add one Secret, with no change to your deployment and no infrastructure to run. Trusted by developers shipping on cloud platforms since 2013.
- One-Secret Setup: Add your QuotaGuard connection URL as a Secret under Tools, and your HTTP and HTTPS clients route outbound calls through it. Register your two static IPs with the destination once.
- No Native Static Egress on Replit: Replit runs your app in a Google Cloud container and hands it a fresh outbound IP on every deploy. There is no platform toggle to reserve one, so a proxy with fixed IPs is the only fix.
- HTTP, HTTPS, and Raw TCP Databases: API traffic routes through the proxy. PostgreSQL, MySQL, and MongoDB connections route through QGTunnel, so your driver connects normally while traffic exits from your static IPs.
- Production-Grade Reliability: A load-balanced pair of static IPs with health checks and automated failover. Both IPs go on the destination allowlist, so your app stays connected through deploys and restarts.
- Shield for Regulated Data: For PHI, cardholder data, or anything under HIPAA, PCI-DSS, or SOC 2 scope, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the data leaving your Replit app. Static is not positioned for regulated data.
Deployment note: This applies to Autoscale, Reserved VM, and Scheduled deployments, which run backend code and support Secrets. Static deployments serve frontend files only and make no outbound calls, so they do not need a static IP. The two static IPs belong to your QuotaGuard subscription, not the Replit container, so they do not change when you redeploy.