Checked 25 October 2026
Short answer
If your coworkers already have accounts on the platform, use its own private sharing: it is a setting. If they don’t, or you want them to sign in with their work account, move the app to TeamOnly. Run npx teamonly init in the exported project and ask your AI tool to “Move this app to TeamOnly”. The screens stay the same; Supabase is replaced by a database and login that come with the app.
01Try this first
Yes, all three can, on a paid plan. The catch is who has to sign in to what.
| How to make it private | Plan | Do coworkers need an account there? | Best when | |
|---|---|---|---|---|
| Lovable | Invite only (up to 10 people per project) on Free and Pro. Workspace or a custom list on Business and Enterprise. | Workspace-only needs Business, from $50/mo | Yes, a Lovable account | Your coworkers already use Lovable |
| Bolt | Private publishing: your Bolt team, people you invite by email, or anyone at a trusted email domain. | Any paid plan. Not with a custom domain | Bolt’s docs don’t say | You want to keep building in Bolt |
| v0 (on Vercel) | Vercel Authentication on all deployments, a password, or company sign-in through Vercel Passport. | Password: $20/mo per project on Pro. Passport: Enterprise | Yes for Vercel Authentication. No with a password | Your team already works in Vercel |
| TeamOnly | Every app is company-only from the first deploy. Whole company or a named list. | Builder $19/mo (3 apps) or Team $249/mo | No. Work Google, Microsoft or an emailed code | Coworkers who don’t have accounts there |
Checked 25 October 2026. Lovable: publishing and plans. Bolt: publishing and private sites. Vercel: deployment protection methods and Passport vs deployment protection. Plans change; check the platform before you pay.
02When to move
If none of that applies, stay where you are. Moving is real work, and the platform’s own sharing is a setting.
03Will my app move?
04How
You need the project’s code on your computer, Node.js, and Claude Code or Cursor.
In Lovable or Bolt, connect GitHub and push the project, then clone it. In Bolt you can also download it as a zip.
In the project folder, run:
npx teamonly init
npm installThis adds the files TeamOnly apps need and instructions your AI tool reads. It never overwrites your files.
Move this app to TeamOnly
It follows the TeamOnly instructions: keeps every screen, rebuilds the Supabase tables in the app’s own database, turns security rules into server checks, removes the login screens, and tells you what it changed and what it couldn’t move.
It runs the app locally. Click through the main screens before you go further.
npx teamonly login
npx teamonly deployYou get a link like tracker.acme.teamonly.app. Coworkers open it and sign in with their work account.
05What changes
| In your Lovable or Bolt app | On TeamOnly |
|---|---|
| Supabase sign-in, sign-up and password reset screens | Removed. TeamOnly signs people in before the app loads; the app reads who they are. |
| Supabase tables | The app’s own database, created on first deploy (SQLite, on Cloudflare D1) |
| Row level security rules | The same checks, written into each server route |
| Supabase storage | The app’s own file storage |
| Edge functions and server functions | Routes in the app’s server code |
API keys in the browser or in .env | Secrets, set with npx teamonly secrets set, never sent to the browser |
| Admin and manager roles | Roles in TeamOnly, given out on the app’s page in the dashboard or with npx teamonly roles |
| Email sent through Resend or SendGrid | Email to coworkers, sent by the app through TeamOnly |
| Scheduled functions | Scheduled jobs, listed in teamonly.json |
| Live updates (realtime) | A Refresh button |
06What we found
We took four public Lovable and Bolt apps from GitHub, from a 3-table job tracker to a 17-table equipment system, and moved each one. All four kept their screens and run behind company login.
Then a fifth test: in a Lovable helpdesk app it had never seen (120 files, 11 tables), we gave a fresh Claude Code session only the one-line request from step 3. It kept all 15 pages, replaced Supabase, said plainly what didn’t come over, and waited for a go-ahead before deploying.
Three of the four had a security problem before the move:
None of that is unusual for a first version, and none of it survives the move: TeamOnly checks the login before any request reaches the app, keys become secrets, and every route checks who is asking.
Not by default. A published Lovable app is public unless you change it. On Free and Pro you can limit it to up to 10 invited people per project; limiting it to your workspace needs Business (from $50 a month) or Enterprise. Visitors sign in with a Lovable account.
Published Bolt sites are public on the Free plan. On paid plans you can publish privately: your Bolt team can see it, plus people you invite by email or anyone at a trusted email domain you add. Sites on a custom domain can only be public.
v0 apps deploy to Vercel, so you use Vercel’s Deployment Protection. Vercel Authentication on all deployments lets in people with access to your Vercel team or project. Password Protection is $20 a month per project on Pro. Company sign-in through Okta or Entra (Vercel Passport) is on Enterprise.
Not automatically. The app moves with an empty database. If the app has an import screen, export your tables from Supabase as CSV and import them. Otherwise ask your AI tool to add one before you move the data.
No. They open the link and sign in with their work Google or Microsoft account, or with a 6-digit code sent to their work email. People who only use apps are free.
Not the moved copy. Once Supabase is replaced, the platform’s editor can’t run it. Keep changing the app in Claude Code or Cursor in plain English, then run npx teamonly deploy again.
For a typical React app, 15 to 60 minutes of your AI tool working in your project, plus you checking the screens. Large apps with dozens of tables and their own password login take longer. The one-minute part is after that: from deploy to a coworker using it.
Early access
TeamOnly is in early access, and every plan is open now. Try it free for 14 days with no card, or subscribe. Either way, your company is ready right away, and three commands put your first app online.
Questions go to hello@teamonly.dev, and a person answers.