Lovable, Replit, Bolt, v0 and their cousins all do the same impressive thing: you describe an app and one exists. They also all hit the same wall, which is that building and running are different problems.
What these tools already handle
More than people give them credit for. Most include some form of hosting, and for a front-end project that is genuinely the end of the story: your app is on a URL, it loads, you can send it to someone.
If that describes your project and it works, you are finished. Do not let anyone talk you into infrastructure you do not need.
Where it stops
Three walls, in roughly the order people hit them.
- 01The sleep wallThe included tier suspends your project when it is idle. Fine for a demo, fatal for anything meant to be running at 3am.
- 02The always-on wallYou added something that has to keep running, a Discord app, a scheduled job, a queue worker. Builder platforms are built around request-response, so this fits badly.
- 03The export wallYou want it somewhere you control, on your own domain, with your own environment variables and no platform branding.
Getting your code out
All of these let you export or push to GitHub. Do that first, before you decide anything else. Code you can move is code you have options about, and it costs ten minutes.
Then pick by shape, not by brand
| WHAT YOU EXPORTED | WHERE IT GOES |
|---|---|
| A static or React front end | Vercel, Netlify or Cloudflare Pages, free |
| A front end with API routes | Vercel, still mostly free |
| An app, worker or scraper | Somewhere always-on, three to seven dollars |
| A front end plus an app | Both: the site is free, only the app costs |
That last row is the common one and it surprises people. You do not have to move the whole project to a paid host because one part of it needs to stay awake. Split it: the site goes somewhere free, and only the always-on part goes somewhere that charges.
The three fixes you will need
An exported vibe-coded project almost always needs the same three edits before it runs elsewhere: secrets moved into environment variables, localhost addresses replaced with real ones, and every dependency written into package.json or requirements.txt.
Paste those three requirements into whichever AI built the project and it will do all of them in one pass. It is a five-minute job once you know what to ask for.
If the always-on part is what moved
That is what Spocket does. Point your assistant at the exported folder, say deploy, and it runs continuously with automatic restarts from $3/mo. No panel to learn, and your environment variables are write-only so the assistant can set them without ever reading them back.