How to Publish a Lovable App for Private Use
Lovable can't put a password on a published app, but it can limit who visits it. In the Publish dialog, choose who can see the website: Invite only (up to 10 people per project on Free and Pro), Workspace on Business and Enterprise, or a custom audience. Visitors then log in to Lovable to get in. For data that must stay private, also require sign-in inside the app and keep RLS on.
By Hire Lovable Xperts · Last verified: 2026-11-17
Can you publish a Lovable app privately?
Yes. Lovable calls it website access: a setting in the Publish dialog that decides who can visit the published app at its live URL. Public is the default. The private options depend on your plan, and each one makes visitors log in to Lovable first. The table lists what Lovable's docs offer as of 17 November 2026.
Website access is separate from project access, which controls who can open the project in the editor. Lovable's docs say the two settings are independent: publishing doesn't change who can edit the project, and it doesn't give visitors access to the project's code.
| Option | Who can visit | Plans | How visitors get in |
|---|---|---|---|
| Public | Anyone with the URL | All plans (the default) | No sign-in |
| Invite only | People you add by name or invite by email, up to 10 per project | Free and Pro | Log in to Lovable with the invited email address, or create a Lovable account with it |
| Workspace | Logged-in members of your workspace | Business and Enterprise | Log in to Lovable as a workspace member |
| Custom | Any mix of the workspace, groups, members and people invited by email | Business and Enterprise | Log in to Lovable |
| Your organization | Members of every workspace in the organization | Enterprise workspaces in an organization | Log in; people outside every workspace join one first |
How do you restrict a published Lovable app, step by step?
Open the Publish dialog and select the visibility row below the Website URL field. That opens the audience picker, where you choose the option and add people. The change applies when you select Publish or Publish changes. You can also ask Lovable in the project chat to change who can see your site, and it applies the change before publishing.
Someone without access sees a “You don't have access” page with a Request access button. Requests arrive in your Inbox, and approving one takes effect at once, without republishing. When you remove someone, Lovable's docs say they can keep access for up to an hour if they're already using the app.
- Open your project and select Publish.
- Select the visibility row below the Website URL field to open the audience picker.
- Choose Invite only (Free and Pro) or Workspace or a custom audience (Business and Enterprise).
- For Invite only, add people by name or invite them by email. Each invited person gets an email with a link and logs in with that address.
- Select Publish, or Publish changes if the app is already live. The new audience takes effect then.
- Open the live URL in a private browser window to confirm it now asks you to log in.
Does restricting the website protect your app's data?
Not on its own. Lovable's docs describe website access as controlling who can visit the published app at its live URL; they don't say it protects your database or API. Treat your backend as reachable by anyone holding the app's publishable key: keep Row Level Security on every table and require sign-in inside the app for anything private.
Two more gaps to close. Preview links skip website access: anyone with an active preview link can open the in-progress version without a Lovable account, unless the link has a password, which Lovable offers on Business and Enterprise only. And the app's own login is a separate thing from website access; Lovable's docs say you add it by asking for authentication in the project chat.
To see whether your tables would leak without the website gate, paste your policies into the free Lovable RLS policy checker.
Related: Lovable RLS and auth best practices
How do you require sign-in inside the app for a private team?
Ask Lovable to add authentication, then stop strangers from creating accounts. On a Supabase project you manage, turn off “Allow new users to sign up”: Supabase's docs say only existing users can then sign in. Invite each teammate instead, and write your policies for the authenticated role, so only people you invited can read the data.
- Ask Lovable in the project chat to add email sign-in and to require it on every page.
- In Supabase Auth's settings, turn off “Allow new users to sign up”.
- Invite each teammate with supabase.auth.admin.inviteUserByEmail, which sends them an invite link. It's an admin method, so call it from an Edge Function, never from the browser.
- If you'd rather keep sign-up open to one company, use Supabase's Before User Created hook to allow sign-ups only from your email domain.
- Write every table's policies with to authenticated (and an ownership check where rows belong to one person), so signed-out visitors get nothing.
Can you password-protect a Lovable app?
Not while Lovable hosts it. Lovable's website access docs say a published app has no password; passwords apply only to preview links, on Business and Enterprise. If a shared password is what your team needs, export the code and host it where the host provides one. Vercel and Netlify both do, on paid plans, as the table shows.
A host password guards the pages, not your Supabase API, so RLS still matters. On Vercel, payment webhooks and other automated callers can't enter a password and get a 401 until you set up its Protection Bypass for Automation.
| Host | Option | Plans and price | Production domain |
|---|---|---|---|
| Vercel | Password Protection | Pro: $20 per month per protected project; included on Enterprise; not on Hobby | Choose All Deployments; the default Standard Protection leaves production domains public |
| Vercel | Vercel Authentication | Every plan | Visitors log in with a Vercel account that has access, instead of a password |
| Netlify | Basic password protection | Pro plans and above; not on credit-based Free and Personal plans | Choose Protect all deploys |
| Netlify | Team login protection (supports SSO) | Enterprise | Visitors log in as members of your Netlify team |
Related: Move a Lovable app to Vercel · Migrate a Lovable site to Netlify
When should an internal app move off Lovable hosting?
Stay on Lovable while Invite only or Workspace access covers who needs in. Consider moving when the access you need is something Lovable's website access doesn't offer: a shared password on the live site, more outside viewers than Invite only allows without upgrading to Business, or a host-level login through your company's identity provider in front of every page.
Moving means exporting the code, rebuilding hosting and cutting over the domain without breaking sign-in. Our Lovable migration service does that in order, with a pre-flight audit of env vars, secrets, auth and RLS and a verified cutover; it's quoted after a free scoping call.
Related: Migration order of operations
Frequently asked questions
Can I make a Lovable app private on the Free plan?
Do visitors need a Lovable account to open a private Lovable app?
Can I put a password on a published Lovable app?
What happens to a private Lovable app if I downgrade my plan?
Does a private published app also hide the project's code?
How do I take a Lovable app offline completely?
Sources
- Lovable Docs — website access: who can visit your published app (read 2026-11-17)
- Lovable Docs — publish your project: audience picker, unpublishing, downgrade FAQ (read 2026-11-17)
- Lovable Docs — control project access: editor access vs website access (read 2026-11-17)
- Lovable Docs — privacy & security settings: default website access, preview links (read 2026-11-17)
- Supabase Docs — Auth general configuration: turning off new sign-ups (read 2026-11-17)
- Supabase Docs — inviteUserByEmail (read 2026-11-17)
- Supabase Docs — Before User Created hook: allow sign-ups by email domain (read 2026-11-17)
- Vercel Docs — Password Protection: plans, price, protecting production (read 2026-11-17)
- Netlify Docs — Password Protection: plans and scope (read 2026-11-17)
Talk to a senior engineer — not a salesperson.
Book a free 30-minute audit call. We'll diagnose what's wrong and tell you exactly what it costs to fix.