All articles

How to deploy your Lovable or Bolt app to production

·3 min read·Jean-Pierre Bonnet
How to deploy your Lovable or Bolt app to production

You spent a weekend with Lovable, Bolt, or Replit. The app works. Someone's excited. Then comes the question nobody warned you about: how do you actually get this thing online for real customers?

The honest answer: going from a working demo to a real, live app involves a handful of technical steps these tools quietly handle for you — right up until the moment real people start using it.

The one idea to take away

A preview link is a sketch you can show people. A production app is the real thing, running safely day and night. They look the same on screen — but they are not the same product.

The demo isn't the finish line

Lovable and Bolt give you a shareable preview link in minutes. That's perfect for showing the idea and getting feedback. It is not somewhere you want paying customers, because it isn't built to stay up, stay secure, or handle real traffic.

"Going live" properly means putting the app somewhere reliable, under your own web address, with the safety pieces switched on.

What "production" actually includes

When we take an app live, here's what's really under the hood — most of it invisible to your visitors, all of it doing a job:

The parts of a live app
Your own domain
yourbusiness.nl — not a random preview address nobody trusts.
SSL (the padlock)
The padlock in the browser bar. It scrambles data so it can't be snooped on, and tells visitors the site is safe.
A real database
Where your data is stored so it survives, instead of vanishing on the next change.
Secrets, kept secret
Passwords and access keys stored safely on the server — never left visible in the page.
Monitoring & alerts
Something watching around the clock that tells us the moment anything breaks.
Backups
Regular copies, so a mistake is an "undo" instead of a disaster.

Where AI-built apps usually break

The pattern is remarkably consistent. The app is fine in the demo and then trips over one of these:

  • An access key was left visible in the app, where anyone could find and misuse it.
  • Pages or data meant to be private were reachable by anyone — there was no real lock on the door.
  • An unexpected error showed a scary blank screen instead of a friendly message.
  • Running costs quietly spiralled because nothing was set to cap them.
  • There were no backups, so one bad change meant starting over.

None of these are reasons to stop building with AI tools. They're reasons to know what you're walking into.

A practical go-live process

This is roughly how we take one of these apps from "works on my screen" to "ready for customers":

1
Review what's there
We read through the app, check for exposed keys and unprotected pages, and note what's missing for real use.
2
Set up the foundations
A proper home for the app (hosting), a real database, your domain, and the padlock (SSL).
3
Lock it down
Move secrets to the server, add log-ins where needed, and handle errors gracefully.
4
Switch on the safety net
Monitoring, alerts, backups, and sensible limits so surprises stay small.
5
Go live & keep it running
Put it on your domain, watch it closely, and fix and improve as real usage comes in.

The demo proves the idea. Production is where it becomes a business.

When to bring in help

If you built something with AI tools and the technical side of going live feels like a wall, that's normal — it's a different skill from having the idea. That gap is exactly the work we do: taking promising AI-built apps and making them solid, safe, and live.

If that's where you are, see how we get AI apps to production, or book a free call and we'll tell you honestly what your app needs.

GDPR CompliantServing BeneluxEst. 2026