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

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.

When should I use an Edge Function?

Last checked 31 Aug 2026

Short answer

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.

The test to apply

Ask: "could a user with dev tools open and tamper with this, or see something they shouldn't?" If yes, it belongs in an edge function, not front-end code.

Clear cases for an edge function

Calling any API that requires a secret key (payment providers, email senders, AI providers without Lovable AI, private REST APIs).
Enforcing business rules that must not be bypassable — e.g. calculating a price server-side rather than trusting a value sent from the browser.
Processing webhooks from external services (Stripe events, form submissions from a third party).
Any action that should be logged, rate-limited or audited centrally.

Cases where you don't need one

Reading/writing your own database tables directly, when RLS policies already enforce who can do what — the Supabase client can call the database straight from the front-end safely, provided RLS is correct.
Pure UI logic and client-side state.
Calling Lovable AI for simple in-app AI features, which is designed to be called without you managing your own provider keys.

A quick decision table

Situation	Approach
Direct table read/write, RLS handles access	Call the database directly
Needs a third-party secret key	Edge function
Must run trusted server-side calculations	Edge function
Simple in-app AI feature	Lovable AI, often no separate function needed

Add an edge function to validate the promo code and calculate the discounted total server-side, instead of trusting the discount sent from the browser

What usually goes wrong

Overusing edge functions for things RLS already handles, adding unnecessary complexity and latency.
Underusing them — trusting a price, quantity or role value sent straight from the client.

Related: /questions/what-are-supabase-edge-functions, /questions/how-do-i-safely-store-api-keys.

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.