vietnamese mud crabsoft-shell crab
2
2 Comments

I stopped paying my AI app builder $25 a month to host a finished app. Here is the math.

I am not a developer. I build in Lovable, and a few months ago I finished an app. It worked, I stopped changing it, and I kept paying $25 a month on Pro. Mostly, it turned out, to keep a custom domain and some AI I no longer used.

Here is the part that annoyed me once I saw it clearly: AI builders do not really charge you to build. They charge you to stay. The credit meter only makes sense while you are actively iterating. Once the app is done, you are just renting.

So I moved the finished app off Lovable hosting. Three things I learned, in case you are sitting on the same bill:

  1. You do not have to migrate your database to move. You can keep Lovable's managed Supabase and move only the frontend to a cheaper host. That keeps the sync working and it is reversible. Moving Supabase to your own instance is a one way door, so only do it if you want full ownership.

  2. The export is just a normal React project. No lock in on the code. The lock in is the confidence gap, not the code.

  3. Two things quietly break on a new host: environment variables (every VITE_ one has to be re added) and Row Level Security policies (re test every read and write as a real user). Fix those two and it just runs.

Result: a flat hosting bill, my own domain, and I dropped Pro once I confirmed I was not iterating anymore.

Full disclosure, I ended up close enough to this problem that I co-founded a host for it, so grain of salt on my part. But the lesson stands even if you never touch what I build: separate where you build from where your app lives. They are two different bills, and the tools want you to treat them as one.

Question for the builders here: for those shipping with Lovable, Bolt, or v0, how much are you paying per month right now for apps you have basically stopped changing?

posted to Icon for group Building in Public
Building in Public
on July 13, 2026
  1. 1

    I like the distinction between paying to build and paying to keep an app alive.

    Those are two very different jobs, but they're easy to mentally bundle together because one tool handles both. Thinking about them separately makes it much easier to choose infrastructure based on where a product is in its lifecycle rather than where it was originally built.

Trending on Indie Hackers
5 days post-launch: Top 50 on Product Hunt, zero signups, and why I think that's actually fine User Avatar 140 comments 641 downloads, 2 sales, and I still don't know why User Avatar 114 comments I built an AI fitness coach, then realized AI was only solving half my funnel User Avatar 80 comments I built a macOS app to make mobile E2E testing less awful User Avatar 59 comments My AI agent quoted a client a price we killed months ago. So I built Engram. User Avatar 31 comments Show IH: I was my AI coding agent's memory — so I automated myself out of that job User Avatar 28 comments