What is vendor lock-in?

When does vendor lock-in stop being theoretical?

Early on, lock-in feels theoretical. It becomes real the day you want to change supplier, raise money and face technical due diligence, or bring engineering in-house. Then three questions decide how hard it is: can you take the code, can you take the data, and are the accounts in your name?

What keeps vendor lock-in from building up?

Lock-in is kept low by owning three things from the start: the code repository, the data in a standard format, and the accounts the app runs on. None of these is expensive to arrange on day one. All three are slow and awkward to win back once a supplier holds them.

• Keep the code in a repository your organization owns. Lovable, for example, syncs to GitHub.
• Prefer open, standard foundations such as PostgreSQL, which many hosts run.
• Register hosting, domains and payment accounts to your company, not to a contractor.
• Get infrastructure billed to you directly.

We work that way by default: you own the code, data and infrastructure, and infrastructure is billed to you at cost. See our plans and pricing.

How locked in is a Lovable and Supabase app?

Less than many platforms, if you set it up deliberately. The code can sync to GitHub, and the data sits in PostgreSQL. Supabase says it relies on standards such as pg_dump and CSV files to make moving in and out easier, and that its cloud service is compatible with the self-hosted version.

• Lovable creates a new repository when you connect GitHub. If you disconnect, the repository keeps its history, but reconnecting makes a fresh one.
• Moving from Lovable Cloud to your own Supabase project is manual: database, storage files, sign-in, secrets and outside services all have to be moved.
• A Lovable Cloud project cannot change region once the backend is on.

Our guide to migrating off Lovable Cloud walks through the move, and what Supabase is explains the parts underneath.

Does the law help you switch cloud providers?

In the EU, yes. The Data Act has applied since 12 September 2025. It requires cloud and software-as-a-service providers to remove obstacles to switching, and platform and software providers must at least let customers export data in a commonly used, machine-readable format.

Switching charges, including data egress fees, may still be charged during a transition period, but they are removed entirely from 12 January 2027. The law helps with the data. It does not put your accounts in your name or hand you the code, so those stay your job.

What does moving off a platform look like in practice?

When the code was handed over and the data is standard PostgreSQL, moving off a platform is engineering work rather than a negotiation. The lesson is the order: portable code, data you can export and accounts in your name come first, and only then does changing host become a project you can plan rather than a rewrite.