Relay.app

QuotaGuard puts your two static IPs onto the target API's allowlist for Relay.app via a small relay you host at the connectivity layer. Because Relay.app's Custom HTTP Request step has no proxy field, the relay forwards each outbound call through QuotaGuard, so the target sees one of your two static IPs instead of Relay.app's rotating egress. Trusted for static IP connectivity since 2013.

• Relay-Based Setup: Host a small relay function on AWS Lambda or a Google Cloud Function, set your QuotaGuard connection URL and a secret key, and point Relay.app's Custom HTTP Request step at the relay URL with two headers, X-Relay-Key holding the secret and X-Target-URL naming the target API. Register your two static IPs with the target API once.
• The Target Sees Static IPs, Not Relay.app's: The relay forwards every request through QuotaGuard, so the target sees your two static IPs. Relay.app's rotating egress and the relay host's own IP never reach the allowlist check.
• Multi-Platform Support: The relay deploys on AWS Lambda or Google Cloud Functions, and the same relay serves Bubble, Zapier, and any other platform that can call a URL but cannot set a proxy. One piece of infrastructure covers them all.
• Production-Grade Reliability: A load-balanced pair of static IPs with automatic failover. Allowlist both, and traffic routes through whichever address responds.
• Shield for Regulated Data: For HIPAA, PCI-DSS, or SOC 2 workflows, QuotaGuard Shield uses SSL passthrough so QuotaGuard never decrypts the data flowing between the relay and the target.

Gate note: You only need this when the API Relay.app calls enforces IP allowlisting. Calls to APIs with no allowlist do not need it.