Emergent
QuotaGuard Static IPs allow your Emergent applications to send outbound traffic through a load-balanced pair of static IP addresses. Once set up, you can use QuotaGuard's IPs to connect to firewalled databases and APIs that require IP allowlisting.
Emergent.sh turns natural language prompts into production-ready applications, but those apps inherit the dynamic IP behavior of cloud infrastructure. Whether hosted on Emergent's managed platform or exported and self-hosted, your app's outbound traffic originates from shared, rotating IP pools.
Common scenarios where you need a static IP:
- MongoDB Atlas: Requires IP allowlisting in Network Access settings
- Payment Gateways: Stripe Connect, Adyen, and banking APIs that only accept requests from registered IPs
- Amazon RDS: Security groups with IP-based rules
- Partner APIs: Corporate firewalls that require known source addresses
- Government Systems: Agencies and healthcare providers with strict IP policies
- Legacy ERPs: On-premise SAP, Oracle, and mainframe systems with firewall restrictions
The result is connection failures and blocked requests that have nothing to do with your code. Your credentials are valid. Your application logic is correct. The external service is simply blocking requests from unknown cloud IP addresses.
QuotaGuard gives your Emergent applications a fixed, verifiable identity that partners can add to their firewall allowlists once.