⚡ TL;DR A gateway fetches data live using encrypted credentials nobody can read back. Apps get opaque keys, OAuth refresh is handled, and the default limit is 1,000 requests a minute per connector per project.
Integrations should not leak keys. Here is how Lovable keeps them locked away.
🔐 The Model
Lovable’s gateway sits between your app and each service, with access matching the connected account’s permissions.
🛡️ Protections
What you get:
- ✅ Encrypted credentials no one can read
- ✅ Opaque connection keys in apps
- ✅ Managed OAuth and token refresh
- ✅ Fixed outbound IP ranges
⏱️ Rate Limits
1,000 requests a minute per connector per project by default; some are lower.
✅ Recommendations
Allowlist gateway IPs, rotate a leaked LOVABLE_API_KEY (the old key works for up to an hour), remove unused connections and restrict browser keys to your domains.
💡 Pro tip Connect with a read-only account when the app only needs to read.
Want an integration security audit? Lord of the Wix can help. ✨
❓ Lovable integration security FAQ
Can admins read credentials?
No.
What is the default rate limit?
1,000 requests a minute.
Are unused connections removed automatically?
No, remove them yourself.
How long does a rotated key keep working?
Up to an hour.
Can I allowlist Lovable IPs?
Yes.
🙏 Credit: Based on public information from the Lovable documentation. Lovable is a product of Lovable. Source: docs.lovable.dev. Lord of the Wix is an independent agency and is not affiliated with Lovable.