How we differ

Make a Lovable app private for your company

Updated 17 October 2026

In Lovable, set the published app to Invite only, or on Business and Enterprise to your workspace, and each viewer signs in with a Lovable account. To let everyone at your company's address in without an account, and log every visit, move the code to Jiayang Cloud: push it to GitHub from Lovable, then run jiayang import.

What follows about Lovable comes from Lovable's docs, read on 16 October 2026 and listed at the end.

What Lovable offers

• On Free and Pro, a published app is Public, which anyone with the address can visit, or Invite only, which only the people you add can visit, after logging in. You add workspace members by name and others by email.
• On Business and Enterprise, it's Public, Workspace or Custom, which combines the workspace, groups, members and email invitees.
• An invited viewer logs in with the invited address, and makes a Lovable account with it if they don't have one.
• You can add up to 10 email invites per update, and each address gets at most 10 invite emails a day.
• Single sign-on is on Business and Enterprise. SCIM is on Enterprise only.

What changes here

• Share with everyone at your company's domain in one step, jiayang share acme/app @example.com, without inviting each person.
• Viewers sign in with a code sent to their address, or with Google or Microsoft. Nobody makes an account first.
• Every signed-in visit is in the audit log with the person's name, on every plan.
• Remove someone and they lose access within 60 seconds, open connections included.
• The app's code gets a signed token saying who is calling. Lovable's own sign-in isn't needed.

When to keep using Lovable

For building the app. Lovable writes it from what you describe. You can keep building there, with the code synced to GitHub, and deploy each change here.

Move a Lovable app here

1. In Lovable, open Project settings, then Git, then GitHub, and select Connect. Lovable makes a new GitHub repository, private by default, and keeps it in step both ways. On a paid Lovable plan you can also select Download codebase instead.
2. Import the repository, or the downloaded folder:

jiayang import https://github.com/you/handbook acme/handbook

The import clones the repository with your own git, so a private one works if you can clone it. It works out how to build the app, usually with Vite, writes jiayang.json, shows you the plan and asks before it makes the app.

Lovable apps often talk to Supabase. Its browser key is meant to be public and becomes an environment variable. Its service key bypasses the database's row rules, so store it as a secret for your project's host and call Supabase from the server side:

jiayang secret set acme/handbook SUPABASE_SERVICE_ROLE_KEY --host <ref>.supabase.co --header apikey

Then share it: jiayang share acme/handbook @example.com. See Make a Lovable app private to your company in the docs.

Sources

1. Publish, Lovable's docs. Checked 16 October 2026.
2. Workspace identity, Lovable's docs. Checked 16 October 2026.
3. GitHub, Lovable's docs. Checked 16 October 2026.

Next

• Import from a repository, in the docs
• How we differ from other ways to keep an app private
• Pricing