Self-hosting: Run your Lovable Cloud project anywhere
Deploy and manage your Lovable Cloud projects on your own infrastructure
Lovable Cloud is designed to be the easiest, fastest, and most enjoyable place to build. Migration is possible because we want you to stay by choice, not necessity.This guide explains how you can self-host and move your Lovable Cloud project to another provider, for example Supabase.
You own your code.
Use our GitHub integration to export your code anytime. Clone, export, and self-host without restriction.
You own your data.
Your database, storage, and configurations can be exported or migrated to another provider.
Lovable is built on open source technologies.
Everything runs on open standards and open-source technologies. No proprietary frameworks, no hidden dependencies.
We earn your trust through quality, not control.Lovable Cloud is designed for speed, simplicity, and reliability. You can build, host, and scale confidently, knowing you can take your project with you.
Includes tables, columns, indexes, RLS policies, functions, triggers
Storage buckets
Automatic via SQL migrations
Includes access policies
Authentication providers
Manual
Reconfigure auth (for example, Google OAuth, GitHub) in your new hosting environment
Environment variables and secrets
Manual
Reconfigure any API keys, tokens, or credentials for external services (for example, Stripe) in your new hosting environment
Data (table contents)
Manual
Export/import as CSV
Storage files
Manual
Download/upload manually
User accounts
Manual, partial
You can export user data from the database, but you cannot export user passwords, so you need to trigger a password reset flow. We recommend you plan the migration before onboarding real users.
Example: Move your Lovable Cloud project to Supabase
You can connect to any backend solution with some technical knowledge. The below steps guide you how to migrate your Lovable Cloud project to Supabase. For more information on Supabase specific steps, see Supabase Documentation.
After migrating your project to your own Supabase instance, you must continue development in your local environment or a preferred IDE. Your project in Lovable remains connected to the original Lovable Cloud database, so any changes made in Lovable after migration will not sync with your new Supabase setup.
Each Lovable Cloud project includes SQL migration files in the supabase/migrations/ folder.Run them in chronological order based on the timestamp in the filename. They are ordered from earliest to latest. For example:
20251008155159_[hash].sql # first - earliest20251008155215_[hash].sql # second
For each migration file in your Lovable Cloud project, follow the steps below:
Copy the entire SQL content from each migration file.
Paste it into the SQL editor in your new Supabase project.
Run and wait for success message.
If a migration fails, check the migration order, table dependencies, and SQL syntax errors.
Export the data from your Lovable Cloud project and then manually import it to your new Supabase project.Export each table with data from your Lovable Cloud project:
Go to Cloud → Database → Table.
Click Export CSV.
Save the file.
Import CSV files to corresponding tables in your new Supabase project:
Go to Table Editor.
For each table, click Insert → Import data from CSV.
If you are using any external services (for example, Stripe) in your Lovable Cloud project, you need to manually reconfigure API keys, tokens, and credentials in your new Supabase project.
In your new Supabase project, go to Edge Functions → Manage Secrets.
# 1. Install Supabase CLInpm install -g @supabase/cli# orbrew install supabase/tap/supabase# 2. Update config files (.env + supabase/config.toml)# 3. Link to your new Supabase projectsupabase loginsupabase link --project-ref your-new-project-id# 4. Push all migrationssupabase db push# 5. Verify schemasupabase db diff
