Lovable.dev Static IPs

No. Static IP proxying must originate from server-side code, not React code running in the user's browser. Frontend-direct calls would expose the proxy credentials. Use a Lovable server-side function, a supported custom connector, or a customer-controlled backend.

Yes. A QuotaGuard outbound identity can follow the backend across supported hosting platforms. Configure secrets and the proxy-aware HTTP client separately in each runtime; setting an environment variable does not automatically route every library or protocol.

Yes. When a Lovable project is connected to Supabase, Lovable deploys server-side operations as Supabase Edge Functions. Store QUOTAGUARDSTATIC_URL in server-side secrets, then configure the exact Deno client and fetch call that opens the protected connection. QuotaGuard has verified this authenticated proxy pattern on current Supabase Edge Runtime versions. The secret protects the credential; it does not route traffic by itself.

Start with Static for ordinary HTTP and HTTPS API allowlisting. HTTPS application payloads remain encrypted to the destination and are not decrypted by QuotaGuard. Static uses the standard HTTP proxy protocol on the client-to-proxy hop. Shield adds TLS protection to that hop and is appropriate when the customer's security review or approved compliance architecture requires it.

Create a subscription, copy the connection URL and assigned addresses, and have the destination allowlist both addresses. Store the connection URL in server-side Secrets and explicitly configure the request client. Setup time depends on the Lovable backend architecture, HTTP library, destination authentication, and firewall approval process.

No.

Your static IP addresses stay the same through plan upgrades and downgrades.

This means you don't need to update your external API allowlists or contact services you're integrating with when you change plans.

The stability matters for Lovable apps because changing IPs at the external service level often requires support tickets and manual review at the API provider, which can take days. QuotaGuard removes that risk entirely.

A stable source address is one security layer, not sufficient authentication. Keep the destination behind HTTPS and retain application authentication and authorization. For high-security environments, use mTLS or short-lived narrowly scoped credentials where supported, exact source, destination, port, and path rules, least-privilege permissions, rate limits, request logs, anomaly alerts, server-side secret storage, and credential rotation. Keep internal databases behind a customer-controlled API rather than exposing them directly.

Yes. Lovable documents gateway-based custom connectors with shared fixed IPv4 185.41.150.0/25 and IPv6 2a07:8241:fca::/48 ranges. Use that native option when the destination accepts the shared ranges and the connector supports the API's request and authentication model. Choose QuotaGuard when the customer needs a much smaller portable allowlist, managed engineering support, selective routing outside the connector model, or customer-only source addresses through Enterprise dedicated infrastructure.

No.

QuotaGuard plans are month-to-month with no minimum commitment or cancellation fees.

You can sign up, configure your addresses, and adjust the plan as your Lovable application grows.