Give WeWeb a Static Outbound IP for API Allowlisting

WeWeb can't set an HTTP proxy on its outbound requests, and it can't run a sidecar next to your app. So when an API partner asks you to allowlist a fixed IP, there's no field in WeWeb to point at a proxy. The fix is a small relay function you host once. Your WeWeb app calls the relay, the relay egresses through QuotaGuard, and the target API sees two static IPs you can allowlist.

WeWeb's REST API Calls Leave From Shared IPs You Can't Allowlist

By default, the REST API plugin makes the call client-side, straight from the visitor's browser. That means the source IP is whoever is using your app right now. There's no fixed address to hand a partner. WeWeb also offers a server-side "Proxy the request to bypass CORS issues" option, which routes the call through WeWeb's own microservice infrastructure. That's shared infrastructure aimed at CORS, not a static egress IP you own. Any native fixed-IP behavior WeWeb exposes on higher workspace plans is still a shared address, pooled across other WeWeb customers, and priced into a plan tier. Check WeWeb's current pricing for the exact plan and cost.

QuotaGuard's relay pattern exists precisely because managed builders like WeWeb never expose an HTTP_PROXY setting or let you run a sidecar process. You get two load-balanced static IPs per subscription, they're the same across every request, and you can reuse them from any other platform you run.

A Hosted Relay Function Gives WeWeb Two Static IPs

The relay is a tiny function you deploy on AWS Lambda or a Google Cloud Function. It reads two headers from the incoming request, forwards the call out through your QuotaGuard connection, and returns the response. Because the outbound hop leaves the relay through QuotaGuard, the target API sees your subscription's two static IPs. Allowlist both.

You don't have to write this from scratch. QuotaGuard publishes a ready-to-run example and documents the full pattern:

• Relay example repo: github.com/quotaguard/static-examples/tree/main/python/lambda-relay
• Relay pattern docs: quotaguard.com/docs/platforms/static-ip-no-http-proxy

The relay egresses through the QUOTAGUARDSTATIC_URL connection string you set as an environment variable on the function:

QUOTAGUARDSTATIC_URL=http://username:password@us-east-static-01.quotaguard.com:9293
X_RELAY_KEY=your-shared-secret

The region in that host (here us-east) is selected when you sign up. Pick the region closest to your target API or database. Changing it later means contacting support at quotaguard.com/contact. You can't swap regions by editing the connection string.

WeWeb Calls the Relay Function URL With Two Headers

In WeWeb, point your REST API plugin call at the relay's function URL instead of the target API. Send two headers. X-Relay-Key is the shared secret that stops anyone else from using your relay. X-Target-URL is the real API you want to reach. The relay forwards the request to that target URL through QuotaGuard.

The request WeWeb issues looks like this:

GET https://<your-relay-id>.lambda-url.us-east-1.on.aws/
X-Relay-Key: your-shared-secret
X-Target-URL: https://api.example.com/v1/orders

Set the method, body, and any target-API auth headers on the WeWeb call as you normally would. The relay passes them through to the target. The only two headers the relay reads for itself are X-Relay-Key and X-Target-URL.

Confirm the Static IPs With One curl Test

Before you wire it into WeWeb, test the relay from your terminal. Point X-Target-URL at QuotaGuard's IP checker. It returns one of your two static IPs, so you know the egress is working:

curl "https://<your-relay-id>.lambda-url.us-east-1.on.aws/" \
  -H "X-Relay-Key: your-shared-secret" \
  -H "X-Target-URL: https://ip.quotaguard.com"

Run it a few times. You'll see both addresses in your subscription's pair. Give both to your API partner to allowlist. Then repeat the same call from your WeWeb REST API plugin and confirm you get the same result.

QuotaGuard Static Pricing Starts at $19/Month

QuotaGuard Static is right for standard HTTPS API calls. On outbound HTTPS the payload is tunneled end to end and never decrypted at the proxy, so your relay traffic stays private. Bandwidth is bundled and there are no per-GB overage fees. QuotaGuard Static direct plans start at $19/month, and the two static IPs work from any other platform you run, not just WeWeb. Dedicated IPs are available on Enterprise and above. On lower tiers, your subscription's two assigned IPs are still static, but shared with other customers.

QuotaGuard Shield Pricing Starts at $29/Month

If your relay carries regulated data, healthcare records, payment details, or anything under HIPAA, PCI-DSS, or SOC 2, use QuotaGuard Shield instead. Shield uses SSL passthrough, so the TLS connection runs end to end and QuotaGuard doesn't decrypt your payload in ordinary operation. Set QUOTAGUARDSHIELD_URL on the relay (port 9294) in place of the Static variable. QuotaGuard Shield direct plans start at $29/month. It costs slightly more than Static at each tier because SSL passthrough adds routing overhead, and the compliance coverage is worth the difference if your data requires it.

All plans include a 3-day trial. Enterprise plans include a 7-day trial. Credit card required. See the full pricing table at quotaguard.com/products/pricing.

Give WeWeb a Static IP Today

WeWeb has no proxy field and no sidecar, so a hosted relay is the honest way to get a fixed outbound IP, and it's reusable everywhere else you build. Deploy the relay, set QUOTAGUARDSTATIC_URL, point your WeWeb REST API call at the function URL with two headers, and allowlist your subscription's two static IPs. Start with the ready-to-run relay example, follow the relay pattern docs, and pick a plan on the QuotaGuard pricing page.