What is Lovable Cloud?

Lovable Cloud is a Supabase backend (Postgres database, authentication, storage, edge functions) that Lovable provisions and manages for your project automatically, with no separate account or dashboard needed.

When should I use Lovable Cloud?

Use Lovable Cloud for most new projects needing a backend — it's the fastest path with no separate account; connect your own Supabase project instead if you already have one, need direct dashboard access, or must integrate with existing Supabase infrastructure.

How do I connect Supabase to Lovable?

In your Lovable project, open the Supabase integration and authorise Lovable to connect to an existing Supabase project (or create a new one), then Lovable can read and write to it the same way it does with Lovable Cloud.

How do I create a database in Lovable?

Ask Lovable to set up Lovable Cloud (or connect your own Supabase project) and describe the tables you need — Lovable provisions the Postgres database and creates the tables from your description.

How do I create database tables?

Describe the table's purpose and fields in plain language to Lovable — including which fields are required, their types, and any relationships to other tables — and Lovable generates the table with appropriate row-level security policies.

How do I view my database data?

Open the Cloud tab (or ask Lovable) to browse tables, edit rows and run SQL directly inside your project — no separate Supabase login needed.

Why isn't Lovable saving data?

Most commonly this is a missing or misconfigured RLS policy blocking the insert/update, an unconnected database, or a form that never calls the backend at all.

Why is Supabase returning a 403 error?

A 403 means Row Level Security blocked the request — the current user's role doesn't match any policy allowing that read or write on that table.

What is Row Level Security (RLS)?

RLS is a Postgres feature that restricts which rows a query can see or change, enforced per-row on the database itself rather than trusted to your app's code.

Do I need RLS on my Lovable app?

Yes, for almost any app with user data, private content or logged-in users — without RLS, anyone can read or write any row via the database's public API.

How do I fix RLS errors?

Identify which operation and role is being blocked, then ask Lovable to add or correct the specific policy for that table rather than disabling RLS.

Why can users see other users' data?

Almost always a missing or too-permissive RLS policy — either RLS isn't enabled on the table, or a policy allows reading rows regardless of who owns them.

How do I safely store API keys?

Store keys as secrets in your backend (Lovable Cloud/Supabase) and call the third-party API from a server/edge function — never put keys in front-end code.

How do I use environment variables?

Use `VITE_`-prefixed variables only for non-sensitive, public values baked into the front-end build; use Secrets for anything sensitive that a server/edge function needs.

What are Supabase Edge Functions?

Edge Functions are small serverless backend functions that run outside the browser — used for anything requiring a secret key, a third-party call, or logic that shouldn't be trusted to the client.

When should I use an Edge Function?

Use one whenever your app needs a secret key, must call a third-party service, or needs logic that shouldn't be trusted to run in the user's browser.

How do I upload and store files?

Ask Lovable to add file uploads and it will wire up storage in Lovable Cloud (or your connected Supabase project), including an upload UI and access policies for the files.

How do I migrate a database?

Last checked 31 Aug 2026

Short answer

Describe the schema change you want in chat and let Lovable write and apply the migration — it handles new tables, columns and RLS policy updates together.

What a migration means here

A migration is any structural change to your database: adding a table, adding or changing a column, adding an index, or updating RLS policies. In Lovable, you don't write raw migration files by hand — you describe the change and Lovable generates and applies it.

How to request one

Add a status column to the orders table (values: pending, shipped, delivered), default pending, and update the RLS policies so only the order's owner can update it

Lovable will:

Generate the SQL for the schema change.
Apply it to your database.
Update or add any RLS policies the change affects.
Update the front-end code that reads/writes the table, if you asked for that too.

Reviewing before applying

For anything on a live app with real data, ask Lovable to show you the migration before running it, and confirm whether it's reversible. Renaming or dropping columns is destructive — back up first (see /questions/how-do-i-back-up-my-lovable-database).

Safe sequencing for bigger changes

Back up or export current data.
Make the change on a small/test dataset if you have a test environment.
Apply it, then verify existing features still work — especially anything relying on the changed column.
Update related RLS policies explicitly rather than assuming they still apply correctly.

What usually goes wrong

Renaming a column that many parts of the app reference, breaking features that weren't part of the original request.
Forgetting that a new column with not null and no default will fail on tables that already have rows.
Assuming RLS policies migrate automatically when they reference a column that no longer exists — check they still make sense afterwards.

Related: /questions/how-do-i-back-up-my-lovable-database, /questions/can-i-move-from-lovable-cloud-to-supabase.

Sources

Was this answer helpful?

You might also need

GuideHow to Create Your First Database TableColumn types, defaults, required fields and relationships — designed so you are not migrating data in three weeks.