Your site lives on Lovable: what you actually own
Your site is live, you like it, all is well. Then you start wondering what happens if the platform shuts down, raises its prices or suspends your account. You do not know whether you can get your work back, in what form, or what you would lose leaving.
The code produced is yours on every plan, including if you stop paying, and it exports. What genuinely deserves your attention is the rest: your site's address, your data, and how your visitors find you. Those three do not export.
Let us start with the good news
The subject carries a lot of online anxiety, so the facts are worth establishing before any nuance.
The code Lovable produces is yours. The publisher states it explicitly, and it holds on every plan including the free one. That is not a commercial favour, it is written in their documentation.
Better still: this code is not an in-house format. It is React and TypeScript, the industry-standard technologies. Any developer can read it, and any host can serve it.
And the exit is designed in: GitHub sync works in both directions, and the complete project downloads. The documentation presents those functions as being for exactly that — back it up, work elsewhere, deploy outside Lovable.
If you came here afraid of being locked in, you can put that down.
What actually happens if you stop paying
This is the most frequent question, and the documented answer is gentler than the rumour.
Downgrading or cancelling does not disconnect your domains and does not unpublish your project. What is live stays live.
The limit sits elsewhere and is worth knowing: connecting a new domain requires a paid plan. In other words, what is already plugged in keeps running, but you do not plug anything new in on free.
And if you bought your domain through them, it belongs to your workspace, not to the project. It is billed separately from the subscription, so a plan change touches neither its registration nor its renewal.
The real inventory, piece by piece
Now that the false worry is out of the way, here is the one that deserves your attention. A site is not only code. It is five things, and they do not travel the same way.
The code. Yours, exportable, standard. Settled.
The address. The most important piece and the most neglected. An address ending in .lovable.app is not yours: it belongs to the platform, and everything you build on it benefits the platform first. A domain of your own costs about ten euros a year and is the only element that follows you everywhere, whatever tool you use three years from now.
The data. Your subscribers, your orders, your content. It does not live in the code: it lives in a database, often at a third-party service plugged into your project. Exporting the code does not carry it along. That is a separate operation, and it is the one people discover on moving day.
The connected services. Payments, email sending, forms. Each has its own account, its own keys, its own billing. They survive the move, but they have to be reconnected one by one.
What you built up with visitors. Your search ranking, your incoming links, the people who bookmarked your page. That value is attached to the address, not to the code. Changing address resets it. Changing tools while keeping the address leaves it untouched.
The question to ask yourself today
It is simple: does the address of my site belong to me?
If yes, you can change tools whenever you like and nobody will notice — not even Google. What you accumulated stays.
If no, your future move will not be a move but a fresh start. The code will leave with you, the reputation will stay behind.
That is exactly why the publisher itself reserves its subdomain for demos, experiments and internal tools, and recommends a domain of your own for a project meant to last. It is not a sales pitch, it is how the web works.
What to do, and when
Now, if your project has a future: buy your domain name. It is the most profitable expense of the whole project, and the only one that loses value by being postponed — because every month spent on a shared address is a month of reputation built for somebody else.
Before plugging anything external in: open the accounts in your own name, not through a platform shortcut. A service connected in your name reconnects elsewhere; a service opened by proxy has to be renegotiated.
Once a month: check that you know where your data is and how to get it out. You do not need to do it, you need to know how. Same logic as knowing how to go back when a site breaks: what counts is not having a backup, it is being able to restore it.