Lovable Preview, Drafts and Testing Agent Share Production Data (Diagram)

Lovable Cloud used to give you two databases, Test and Live, so the things you built with could be pointed at junk data. On October 5, 2026 that split was retired. The diagram shows what took its place: one database, with every way you try a change pointed straight at it.

A flowchart of where Lovable Cloud writes data since October 5, 2026. Three boxes sit along the top: a red testing agent signed in as your only user, an amber draft with separate code but shared data, and an amber preview. All three arrows land on one green database holding the rows your customers use. The testing agent's arrow is thick, red and labelled clicks and submits as you. A dotted arrow labelled until Oct 5 runs from the preview to a dashed grey old test database, detached October 5 and deleted November 4.
Three ways to try a change, one database underneath them, and it is the one your customers are using.Full explanationMermaid source

Reading the diagram

Start at the bottom. The green cylinder is your customers' data. Green marks the thing worth protecting, and it is the only database left in the picture that anything still writes to.

Right, amber: the preview. Lovable's preview docs call it "your app's staging environment", then say "the preview and your published app share the same backend and data." It is staging for your code, not for your data. The dotted arrow is where its writes used to go. That path ended on October 5, which is why the old test database is drawn dashed and grey: Lovable detached it that day and deleted it for good on November 4.

Middle, amber: drafts. Drafts launched in September as the nearest replacement for Test and Live, and the label says what they separate. Code changes wait until you accept the draft. Data changes don't wait for anything: the drafts docs say a draft "uses your project's real data". Amber marks both of these as places to be careful, not places that are broken.

Left, red: the testing agent. This is the one edge drawn thick and red. Since September 8, browser testing can sign in to your app and "Fill inputs and submit forms". With exactly one user in the app, it signs in as that user, and on a new project the only user is usually the founder, with admin rights. It is red because it acts on its own, holding your account, on the data the green box holds.

None of this is a vulnerability. The point of the picture is the convergence: three arrows that used to have somewhere safe to land now share one target.

What to do with it

Give the agent a second, non-admin user so it stops defaulting to you, and tell it out loud which buttons it must not press. For a risky change, remix the project: Lovable's docs say a remix copies table structure but no rows and no users, which is the only empty database left. The full walkthrough, with a prompt to paste before testing, is in Lovable Retired Test and Live.

The Mermaid source

Copy this and relabel the boxes for your own setup.

---
title: "Everything you test with hits production"
---
flowchart TB
    P["Preview<br/>the app you click<br/>while building"]
    D["Draft<br/>separate code,<br/>shared data"]
    A["Testing agent<br/>signed in as your<br/>only user, often you"]

    DB[("One database<br/>the rows your<br/>customers use")]
    T[("Old test database<br/>detached Oct 5,<br/>deleted Nov 4")]

    P -->|"rows you add<br/>are real"| DB
    D -->|"real data,<br/>not a copy"| DB
    A -->|"<b>clicks and<br/>submits as you</b>"| DB
    P -.->|"until Oct 5"| T

    classDef private fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#1c1917
    classDef public fill:#fef2f2,stroke:#ef4444,stroke-width:2px,color:#1c1917
    classDef gate fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#1c1917
    classDef store fill:#f5f5f4,stroke:#57534e,stroke-width:2px,color:#1c1917,stroke-dasharray:5 5

    class DB private
    class A public
    class P,D gate
    class T store

    linkStyle 2 stroke:#ef4444,stroke-width:3px

Does the Lovable preview write to my production database?

Yes. Lovable's preview docs say the preview and your published app share the same backend and data, and since October 5, 2026 that is true for every Lovable Cloud project. A row you create in the preview is a real row.

Do Lovable drafts have their own database?

No. Lovable's drafts docs say a draft uses your project's real data. A draft keeps code changes separate until you accept it, but any data you add or change while testing it is real immediately.

Which account does the Lovable testing agent use?

If your app has exactly one user, Lovable signs in as that user, which on a new app is usually the founder's admin account. Once there is more than one user, it asks which account to use, so a separate non-admin test user is the simplest safeguard.

Where did the Lovable Test database go?

Lovable detached existing Test databases on October 5, 2026 and said it would restore one on request until November 4, 2026, after which they are permanently deleted. That is the dashed box in the diagram.

Your preview is production now

Scan your published Lovable URL for a leaked service_role key, exposed secrets and missing headers before the next test run touches real data.

diagrams

Lovable Preview, Drafts and Testing Agent Share Production Data (Diagram)