⚡ TL;DR Build secrets are workspace-level variables available only during builds, often npm tokens referenced in .npmrc. The managed registry gives Enterprise workspaces a private npm registry.
Private code needs private packages. Here is how Enterprise teams get them.
🔑 Setting Up Build Secrets
Workspace settings, Build & deploy, Build secrets, New variable, then reference ${NAME} in .npmrc. Owners and admins only.
📏 Build Secret Rules
Workspace-wide, build-time only, hidden after saving and not renameable; deleting one breaks builds that use it.
📚 Managed Registry
Provision it under Build & deploy, Managed registry, create and save a service key, then configure .npmrc and npm-key.json. Scoped packages are supported.
🏢 Plans
Both are Enterprise only. External registries such as GitHub Packages need a build secret token.
💡 Pro tip Use project secrets for runtime keys; build secrets never reach the live app.
Setting up Lovable for an enterprise codebase? Lord of the Wix can help. ✨
❓ Lovable build secrets FAQ
Which plan has build secrets?
Enterprise.
Are they available at runtime?
No.
Can Lovable read them?
No.
What is the managed registry?
A private npm registry.
Can a build secret be renamed?
No.
🙏 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.