From Localhost to Live: What It Actually Takes to Ship Your AI-Built App
A practical breakdown of everything that stands between your working prototype and a real URL. What you can handle yourself, what you probably can't, and where to get unstuck.
Deploying an AI-built app requires five things: a hosting platform, a domain, a database that isn't on your laptop, environment variables configured correctly, and a deploy process that doesn't break. Most of these are a one-time setup if you know what you're doing.
Your app works. It's been working for days. You've shown it to people. Everyone says build this.
What you have is a localhost:3000 URL that only your laptop can see.
Here's everything that stands between where you are and a real URL other people can visit.
The hosting platform
Your code has to run somewhere. Your laptop can't be on all the time serving requests to strangers.
For most AI-built apps, the right answer is Vercel. It handles the server infrastructure automatically, deploys your code every time you push an update, and gives you a real URL within minutes. For simple apps it's free. For production apps with real traffic it's $20 a month.
Railway and Render are good alternatives if your app runs as a server rather than a serverless function. The difference matters and your AI probably didn't explain it.
The wrong answer, for most people reading this, is a VPS. A VPS is a blank server you have to configure yourself. The AI will cheerfully configure it incorrectly.
The domain
The URL Vercel gives you is a free subdomain. If you want your-app.com instead, you need to buy the domain and connect it.
Buying the domain takes five minutes. Connecting it to Vercel takes another ten if you know what you're doing. DNS propagation takes up to 48 hours, which means you make the change and then wait. The AI tends to announce success at the "I made the change" step.
SSL, the padlock in the browser address bar, is handled automatically once the domain connects. Don't let anyone charge you separately for this.
The database
If your app stores any data, that data is probably sitting in a SQLite file on your laptop right now.
SQLite is fine for development. It doesn't work in production on most hosting platforms because the file disappears when the server restarts. You need a real database, something like PostgreSQL hosted on Supabase or PlanetScale, that lives separately from your app.
Migrating from a local SQLite database to a hosted PostgreSQL database is the step where the most people get stuck. The AI will write you a migration script. Whether it runs correctly on your specific data depends on things the AI can't see.
Environment variables
Your app almost certainly has secrets. API keys, database connection strings, authentication tokens. If any of these are written directly in your code, that's a security problem. If they're in a .env file on your laptop, they need to be somewhere else before anyone else can run your app.
Every hosting platform has a way to configure environment variables through their dashboard or CLI. Vercel has a simple interface. The variables have to match exactly what your code is looking for, including the names, and they have to be set in the right environment. Development and production are separate.
This is the most common reason apps work locally and fail immediately after deploying. The app boots, tries to connect to a service using a key that doesn't exist in the production environment, and crashes.
The deploy process
Once you have the platform, domain, database, and environment variables in place, deploying should be one push to a git repository.
The one-time setup to get there is where people spend their two weeks.
What you can do yourself
If you're comfortable with a terminal and you're willing to spend an afternoon reading documentation and troubleshooting, you can set all of this up yourself. Vercel's documentation is good. The concepts aren't that complicated once you understand what each piece does.
If you've already spent two days on this and you're not sure which of the five things above is actually broken, that's the harder situation. Debugging a half-configured deployment without knowing what a correct configuration looks like is slow and frustrating.
What I can do for you
I do this for people who've built something with an AI tool and can't get it live.
One session. I get your app deployed to Vercel, connected to your domain, wired up to a production database, and configured with your environment variables. You end up with a real URL and a process you can maintain going forward.
If you're stuck, tell me what you've built and I'll tell you what it would take to ship it.