QuotaGuard and Lovable Integration Guide
A Lovable app does not have its own outbound egress to attach a static IP to. The static IP attaches one layer down, where your server-side code actually runs. This guide points you to the right place.
What Is Actually Making the Outbound Call
Lovable generates a React and TypeScript frontend. The browser talks directly to managed backend services, and your server-side logic, including any call to an external API, typically runs in Supabase Edge Functions when you use Lovable Cloud or managed Supabase. The browser’s IP is the end user’s, which is not something you allowlist. The address a partner API sees is the Supabase Edge Function’s egress, not Lovable’s.
So when an IP-restricted API rejects your Lovable app, the fix is to give the Supabase Edge Function a static IP, not Lovable.
Follow the Supabase Edge Functions Guide
If your Lovable app uses Lovable Cloud or managed Supabase for its backend, the outbound calls run in Supabase Edge Functions on the Deno runtime. QuotaGuard provides a native SOCKS5 static IP path for Deno.
See the QuotaGuard and Supabase Edge Functions Integration Guide.
If You Exported and Self-Host
If you exported your Lovable project to GitHub and self-host the app, the static IP attaches to whatever host runs your server-side code. Follow that platform’s guide:
The same two QuotaGuard static IPs work across all of these, so a partner allowlists one pair no matter where your backend ends up.
Ready to Get Started?
Get in touch or create a free trial account.