One in Eight Businesses Naming an AI App Builder Wants Out. The Database Underneath, They Keep.

One in Eight Businesses Naming an AI App Builder Wants Out. The Database Underneath, They Keep.

Lovable, Replit and Base44 get businesses to a working app. About one in eight that name them now want to move off, and they take the stack with them: React, Supabase, Stripe. The opening is the door out, not another way in.

A kids' video streaming app is built on Base44. It works, and people use it.

The request on the table is short: move it to an independent Supabase backend, off the platform and its fees.

Not a rebuild. Not a new idea. A move.

It is not a rare request. Right now, about one in eight businesses that name an AI app builder want to move off it. Lovable, Replit, Base44, Bolt, v0: the tools that turn a prompt into a working app are being named more often than before. They are also being left far more often than the stack they generate.

What gets left, and what stays
1 in 8AI app builder mentions that ask to leave itLovable, Replit, Base44, Bolt and v0 together
1 in 180Supabase mentions that ask to leave itThe database these builders set up for you
1 in 5Base44 mentions that ask to leave itThe most-left builder of the group

Tools named in live market demand.

They leave the builder, not the app

Read what these businesses want next and a pattern shows up fast.

They keep what the builder made. The React front end. The Supabase database. Stripe for payments. A quarter of them name those same parts in the very request that leaves the builder.

What they leave is the room the app was made in.

The prompt was never the product. It was the scaffolding, and scaffolding comes down.

How often a named tool is one the business wants to leave

The builders sit at the top. The stack they generate sits at the bottom.

The destinations split in two. Apps go to their own code repository and their own cloud: AWS, Azure, Google Cloud, a self-hosted Postgres. Sites go somewhere a marketing team already knows: WordPress, Framer, Webflow, with every blog post and every URL carried over.

Either way, the move is about owning the thing. The data was always in Supabase. Now the code has to live somewhere the business controls too.

The layer people leave is the one that made the start easy

This is not a story about bad tools. Base44 and Lovable did their work. A founder with no engineering team shipped something real, and real customers showed up.

That is exactly when the builder stops fitting.

The part that made day one easy is the part that gets left. The part that holds the data is the part that stays. Builders of every kind of software can use that line, whatever they make.

What to build for the businesses already leaving

The market is asking for a door out, and it is walking past most of the products that could be one.

  • An eject button that works. One action that turns a Lovable or Base44 app into a clean repository, with the Supabase project, the Stripe keys and a deploy pipeline intact.
  • Hosting made for AI-built apps. Staging, logs, backups and rollbacks for apps whose authors never set any of that up, priced for a founder with ten paying customers.
  • A site move that keeps search traffic. A converter that takes a prompt-built site with a hundred posts to WordPress or Webflow without breaking a single link.

If your product is where someone starts, plan for the day they outgrow it.

If it is where their data lives, you are the part they keep.