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.

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 safely store API keys?

Last checked 31 Aug 2026

Short answer

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.

Why this matters

Any string that ends up in your app's front-end code — including anything in a .env file prefixed for the browser — ships to every visitor and is visible in browser dev tools. API keys, especially ones with billing or write access, must never live there.

Where keys belong

Lovable Cloud (and connected Supabase projects) provide Secrets: encrypted values stored server-side and injected only into server/edge functions, never into the shipped front-end bundle.

Ask Lovable to add the integration you need, e.g. "Connect Stripe and store the secret key securely."
Lovable creates a secret slot and an edge function that reads it server-side.
Your front-end calls that edge function; the actual third-party key never reaches the browser.

Add a Resend integration for sending emails. Store the API key as a secret and create an edge function to send the email — don't expose the key to the client.

Secrets vs environment variables

VITE_-prefixed environment variables are bundled into the client and are not secret — they're readable by anyone. Use them only for genuinely public values like a public API base URL. Use Secrets for anything sensitive.

What usually goes wrong

Pasting a key straight into a component or a VITE_ variable "just to test it" and forgetting to move it before publishing.
Calling a paid third-party API directly from the browser, which both exposes the key and lets anyone rack up usage on your account.
Assuming a key is safe because it's not printed to the console — the bundled JavaScript itself can be inspected.

Lovable's security review flags exposed keys before you publish, but don't rely on it as your only check — review any integration you set up manually.

See also /questions/how-do-i-use-environment-variables and /questions/what-are-supabase-edge-functions.

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.