You described what you wanted, the AI built it, and there it is running on your laptop, looking finished. Then the question arrives that no prompt ever answered for you: where does this thing actually live, so someone other than you can open it in a browser?

That gap catches almost everyone who builds with AI. The tool was brilliant at making the app and completely silent on putting it online. So let us fill in the missing half, cheaply and honestly.

The AI built the app, not the hosting

Getting software onto the internet is a separate job from writing it, and the vibe-coding tools do not do that job. Your app on your laptop is talking to a database on your laptop, using secrets stored on your laptop, reachable only by your laptop. A real deployment means a server somewhere, a real database, a proper web address, and the whole thing staying up when your machine is off. None of that was in what the AI generated for you.

The good news is that it is far less expensive and far less mysterious than it looks.

Do not overpay just to get online

The reflex, when you hit this wall, is to reach for a platform that promises a one-click deploy. Those are genuinely easy, and for some projects they are the right answer. But the bill climbs quickly as you grow, you are locked into one company's way of doing things, and a full app with its own backend often does not fit neatly into them anyway.

For most vibe-coded apps, the honest starting point is a cheap virtual server. It costs a few dollars a month, it is a machine you own outright, and it runs your whole app, front end, backend and database, in one place.

Where to actually start

You do not need much. A four dollar server comfortably runs a vibe-coded app or a blog with modest traffic, and it is the right place to begin. Here is what a $4 VPS actually runs and how to make it work. When your app grows and wants more room, you move up to the next tier in a couple of clicks, no rebuild and no lock-in. Here is what a $6 VPS handles once you are there.

Start at the bottom, in other words, and let real usage decide when to spend more.

What breaks on the way to launch

This is the part worth reading twice, because these are the exact things that trip up a first launch of an AI-built app:

  • Secrets and settings. Your API keys and passwords are probably sitting in the code or in a local file the server does not have. On the server they need to be set properly, or the app either fails or leaks the keys.
  • The database. The app likely used a simple local database while you built it. In production you need a real one, and the setup steps that create its tables have to actually run against it.
  • HTTPS. Your laptop had no certificate and did not need one. A live site does, or browsers will warn people away. This is where a server like Caddy earns its place, because it sorts out HTTPS for you automatically. Our droplet deployment guide walks through exactly that.
  • Keeping it running. Right now your app runs because a terminal window is open. On a server it needs to run as a proper background service that restarts on its own if the machine reboots.
  • Security. AI-generated apps often ship with the doors unlocked, debug mode left on, endpoints exposed, weak or missing checks on who can do what. Worth a careful look before real people arrive.

None of these are hard once you know they exist. All of them are quietly waiting if you do not.

Two honest ways forward

Learn it yourself. It is genuinely learnable, and cheaper than you think. Start with the $4 VPS guide to pick a server, then the deployment walkthrough to get it live. A weekend and some patience will get most vibe-coded apps online.

Or get a hand. If you would rather your app was built on solid ground and simply got to launch without you learning server administration, that is exactly what we do. We set up a proper foundation, handle the deployment, the database, the secrets and the security, and get you live. You can read how that works here.

Either way, the takeaway is the same: your app deserves to be online and to hold up when real people use it, and you do not need expensive hosting to get there. Start cheap, know what deploying actually involves, and launch the thing.