Hire Lovable Xperts
Deployment

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.

Lovable website access options (Lovable docs, read 2026-11-17)
OptionWho can visitPlansHow visitors get in
PublicAnyone with the URLAll plans (the default)No sign-in
Invite onlyPeople you add by name or invite by email, up to 10 per projectFree and ProLog in to Lovable with the invited email address, or create a Lovable account with it
WorkspaceLogged-in members of your workspaceBusiness and EnterpriseLog in to Lovable as a workspace member
CustomAny mix of the workspace, groups, members and people invited by emailBusiness and EnterpriseLog in to Lovable
Your organizationMembers of every workspace in the organizationEnterprise workspaces in an organizationLog 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.

  1. Open your project and select Publish.
  2. Select the visibility row below the Website URL field to open the audience picker.
  3. Choose Invite only (Free and Pro) or Workspace or a custom audience (Business and Enterprise).
  4. 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.
  5. Select Publish, or Publish changes if the app is already live. The new audience takes effect then.
  6. 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.

  1. Ask Lovable in the project chat to add email sign-in and to require it on every page.
  2. In Supabase Auth's settings, turn off “Allow new users to sign up”.
  3. 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.
  4. 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.
  5. 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.

Password protection after you export the app (host docs, read 2026-11-17)
HostOptionPlans and priceProduction domain
VercelPassword ProtectionPro: $20 per month per protected project; included on Enterprise; not on HobbyChoose All Deployments; the default Standard Protection leaves production domains public
VercelVercel AuthenticationEvery planVisitors log in with a Vercel account that has access, instead of a password
NetlifyBasic password protectionPro plans and above; not on credit-based Free and Personal plansChoose Protect all deploys
NetlifyTeam login protection (supports SSO)EnterpriseVisitors 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?
Yes. Free and Pro plans offer Invite only website access, for up to 10 people per project. You add them by name or invite them by email, and they log in to Lovable to open the app.
Do visitors need a Lovable account to open a private Lovable app?
Yes. Invite-only visitors log in with the invited email address or create a Lovable account with it, and Workspace access admits only logged-in workspace members. Only a Public app can be visited without signing in.
Can I put a password on a published Lovable app?
No. Lovable's docs say a published app has no password. Passwords exist only for preview links, on Business and Enterprise plans. For a password on the live site, host the exported code on a service that offers one, such as Vercel or Netlify on a paid plan.
What happens to a private Lovable app if I downgrade my plan?
Lovable's publishing docs say an app restricted to workspace members or selected people keeps requiring login after a downgrade. Invited people, the project owner, workspace owners and people the project is shared with directly keep their access.
Does a private published app also hide the project's code?
Website access and project access are separate settings. Restricting who can visit the app doesn't change who can open the project in the editor, and publishing doesn't give visitors access to the code.
How do I take a Lovable app offline completely?
Unpublish it: go to Project settings → Publishing → Unpublish project → Unpublish. The live URL stops working and the project stays in the editor, so you can publish again later.

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.

Or hire a Lovable developer for the whole job →

Book a free audit call