Vibecode to production · Lovable

Your Lovable app has
to face the world.

Lovable takes you from an idea to something clickable in an afternoon. That is genuinely impressive, and it is also exactly where it stops: a demo on a lovable.app address is not yet a product with customers on it. Your own domain, hosting you control, data that is not open to everyone and code that belongs to you — that is the step after.

100%
Code and repository in your name
2-6
Weeks from export to live
0
Screens you have to draw again
30
Days of support after delivery
Vibecode naar productie
0:00 / 0:00

In half a minute I show what almost always sits below the waterline in a project like this: everyone can reach all the data, payments that only work in the demo, and an environment that does not run outside the tool.

Recognise it? Send your link. The first opinion costs you nothing.

Sound familiar

Where Lovable projects get stuck.

01

It still lives on lovable.app

You can connect a custom domain, but the site keeps running on their infrastructure, behind their subscription. If the subscription stops, your website stops — a risky place for something customers rely on.

02

The data is wide open

Lovable puts Supabase underneath, which is a sound choice. What rarely gets set properly are the per-table permissions. Without row-level security, anyone who lifts your public key out of the source can read the whole table.

03

Google sees nothing

What Lovable delivers is usually an app that assembles itself in the browser. There are no separate pages with their own titles and copy, so there is little for Google to index and your visibility lags behind.

04

Every prompt breaks something else

By the tenth change the model touches files that were already fine. Without commits that mean something you cannot go back to yesterday's version, because you no longer know which one that was.

05

The export is a pile of code

You can export to GitHub, and then you have code. What you do not have is a build process, environment variables, migrations, and someone who knows which part of it actually matters.

06

Payments and email are missing

A button saying 'Pay now' is not a payment. Stripe or Mollie, webhooks that track whether the money arrived, and email that does not land in spam: that is server work which never existed in the preview.

How it works

From lovable.app to your own domain.

01

Export and assessment

You connect your GitHub or send the export. I read what is there and tell you what is usable: screens, flow and data model almost always survive. That assessment costs you nothing and is not a sales pitch for a rebuild.

02

A foundation underneath

Supabase with row-level security per table, real migrations, secrets out of the source, and server-side code for everything a visitor should not see. This is where the gap between demo and product closes.

03

Made findable

Server-rendered pages with their own titles, descriptions, sitemap and structured data. Precisely the part a browser app lacks, and where your organic visitors come from.

04

Your own domain and hosting

Domain in your name, hosting on your account, repository in your GitHub, monitoring on top. From that moment you can switch builders without rebuilding anything.

What you end up with
  • ✓A site that runs independently of Lovable
  • ✓Your own domain and hosting account
  • ✓Data behind per-user permissions
  • ✓Indexable by Google
  • ✓Repository in your name
  • ✓Fixed price, known up front

What it costs depends on how much has to be finished and how many integrations come with it. Half an hour of looking is enough for me to name a fixed number.

No need to start over

Your prototype is worth the work.

The reflex with an AI prototype is to throw it away and start again properly. That is almost never necessary and usually more expensive. What you worked out in Lovable — which screens you need, in what order, with which fields — is the substantive part of the job. That stays. What is missing underneath, I add: permissions, migrations, server-side code, tests and a deploy that does not fall over the moment someone other than you opens it.

Frequently asked questions
Can I move my Lovable project to a custom domain?
Yes, and there are two flavours. Inside Lovable you connect a custom domain to their hosting; your site then stays dependent on their subscription. The other route is to export and put it on your own hosting, after which domain, account and code are all yours. For anything customers need to reach, I recommend the second.
How do I export my Lovable project?
Lovable connects to GitHub and writes your project to a repository on your account. That gives you the code, but not yet a working setup outside it: environment variables, build settings, database migrations and the server side are usually missing. That is exactly the part I add.
Where is the best place to host my Lovable app?
For a Next.js or React project Vercel works most comfortably, with Supabase for the database. Both accounts end up in your name and you pay the supplier directly, with no markup through me. If you want everything to stay inside the EU, that is possible; we pick the region accordingly.
Can you take over my Lovable project without starting from scratch?
Usually yes. Lovable generates React with Tailwind and Supabase underneath, which is the stack I work in daily. I keep your screens and your data model and build the foundation under them. Only if the data model genuinely does not match what you want is a fresh start cheaper — and I will say so.
Is my data in Lovable safe?
That depends entirely on the permissions on your Supabase tables. The key sitting in your frontend is public by design; row-level security is the only thing deciding who may see what. It is the first thing I check in the scan, because it is the problem that most often goes live unnoticed.
Will my Lovable site be found on Google?
Not on its own. An app that assembles itself in the browser gives Google little to read: no separate URLs with their own titles, no sitemap, no structured data. While finishing the build I move the pages to server-side rendering, so each page has its own address and its own text.
What does finishing a Lovable project cost?
Finishing usually takes two to six weeks and gets one fixed number up front. If you do not know what is needed, you start with a Discovery; that amount comes off in full if you go ahead with the build.
Can I keep working in Lovable afterwards?
For trying out new screens, absolutely. For the production environment, no: that lives in your repository, with migrations and tests an AI tool would walk straight through. In practice people keep using Lovable as a sketchpad afterwards, just not as hosting.
Let's build

Tell me what you
want to build.

A half-hour call. You get an honest answer about what it costs, how long it takes and whether building it is smart at all.

bas@webframer.nl+31 6 47 00 62 07
Free · no obligation

Have your current site or tool scanned

You do not have to want to buy anything yet. Send what you have and I will tell you honestly what I would keep, what I would replace and whether that is worth the investment. Including when the answer is that you are better off doing nothing.

The scan is a first impression, not a security audit.

WhatsApp
0:00 / 0:00
  1. 01Send a link to your site, your tool or your repository
  2. 02I look at speed, structure, data and security
  3. 03Usually within two working days you hear what I would replace and what that costs
Vibecode naar productie
0:00 / 0:00
Turn your Lovable project into a real website · Webframer