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.

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 back up my Lovable database?

Lovable Cloud stores backups you can restore from directly in the Database screen; for extra safety, also ask Lovable to export your data periodically.

How do I migrate a database?

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.

Can I move from Lovable Cloud to Supabase?

Yes — Lovable Cloud is a Supabase backend under the hood, and Lovable supports connecting your own Supabase project instead, though moving existing data across takes an export/import step.

How do I connect Supabase to Lovable?

Q: 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.

Last checked 31 Aug 2026

Short answer

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.

When to do this instead of using Lovable Cloud

Connect your own Supabase project if you already have one with existing data/users, need direct Supabase dashboard access, or have infrastructure requirements Lovable Cloud doesn't fit. See when should I use Lovable Cloud if you're still deciding.

Steps

In your Lovable project, find the Supabase integration option (or ask in chat).
Authorise Lovable to access your Supabase account.
Choose an existing project, or let Lovable help create a new one.
Once connected, describe what you need built:

Connect this project to my existing Supabase project. Create a customers table matching the structure I already have for users.

Lovable can now generate tables, edge functions and auth flows against that Supabase project, the same way it would with Lovable Cloud — the difference is you retain full dashboard access to that Supabase project outside of Lovable too.

Migrating an existing schema

If you have existing tables, describe them precisely (column names, types, relationships) or export the schema so Lovable can match it exactly rather than guessing structure from a vague description.

What usually goes wrong

Row-level security surprises: an existing Supabase project may have RLS policies (or the lack of them) that don't match what a Lovable-generated feature expects — review policies after connecting, especially on tables Lovable didn't create.
Conflicting schema changes: if you or a teammate also edit the Supabase dashboard directly, changes can diverge from what Lovable expects — keep schema changes in one place where possible, or tell Lovable about dashboard edits so it stays in sync.
Auth provider mismatches: if your existing project uses custom auth configuration (social providers, custom SMTP), confirm those still work as expected once Lovable is generating auth-related code against it.

For a non-trivial existing Supabase project, it's worth having PromptSites.com review the connection and RLS policies once, rather than discovering a security gap after launch.

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.