Orbit

It works on localhost. How do my friends open it?

Chris Rupp

Your app finally works. you’ve been clicking around in it for an hour, the login works, the buttons work, it’s real. So you text your friend the link… localhost:3000. They tap it and get “This site can’t be reached.” You open it again on your laptop and it’s fine. So what’s going on, and how do your friends actually open the thing?

What localhost actually means

Localhost means “this computer.” Not your computer… THIS computer, whichever one is reading the link.

That’s the whole trick. Every device has its own localhost, it’s a built in shortcut that points a device back at itself. On your laptop, localhost:3000 means “the thing running on my laptop, on door number 3000” (the 3000 is called a port, think of it like a door number on the same building). Your app is running there cuz your agent started it there when it ran the dev server.

On your friend’s phone, localhost means their phone. Their phone looks at itself, checks door 3000, finds nothing, and gives up. Your app isn’t broken, it’s just not on their phone, and it was never going to be. The link was basically “come over to my house” with no address.

And even if they had your laptop’s real address, it still wouldnt work for long. Your laptop sits behind your home router, it goes to sleep, you close the lid and walk away… it was built to be your computer, not a place the whole internet can visit.

Your app needs a home on the internet

That’s what hosting is. A host is a company that runs computers that are always on, always connected, and meant to be visited by anyone. Vercel, Netlify and Cloudflare Pages are the big names you’ll hear for this kind of app.

They do three things for you:

Your friend taps that, and there’s your app.

Getting it there is called deploying

Deploying just means putting the new version of your app on the host. You could do it by hand every time, but you dont have to.

Connect your GitHub repo to Vercel once. After that, every time you push to GitHub, Vercel notices, grabs the new code, builds it, and puts the new version up by itself. That’s why it’s worth having your project on GitHub in the first place… GitHub becomes the one place your code lives, and the host just watches it for changes.

Or honestly, just ask your agent. Something like:

“deploy this to vercel and give me the link. if the build fails, show me the error and fix it.”

Your agent can set the whole thign up, and you’ll mostly just be clicking “authorize” a couple times.

Want your own name?

myapp.vercel.app works, but maybe you want myapp.com. Buy that domain from any domain seller, then point it at your host with DNS.

DNS is the internet’s phonebook. Computers dont actually find each other by names, they use numbers (IP addresses), and names are just for us humans cuz a long string of numbers is impossible to remember. So when your friend types myapp.com, their phone asks the phonebook “where is myapp.com?”, the phonebook says “over at your host,” and your app opens.

Pointing your domain at your host just means adding an entry to that phonebook. Your host will tell you exactly what to add, and your agent can walk you through it. Fair warning, sometimes it takes a little while for the change to show up everywhere, so don’t panic if it doesnt work in the first few minutes.

One catch: a failed deploy looks like nothing happened

If a deploy fails, your site keeps the last version that worked.

That’s on purpose, and it’s actually a good thing. The host builds the new version off to the side first, and only swaps it in once the build succeeds. If the build breaks halfway through, the swap never happens, so your friends keep seeing the old working app instead of a broken one. Way better than a blank page.

But here’s where it bites you. Your agent says done, the code is on GitHub, and your friend opens the link and sees… no change. The new version never went live cuz the build failed, and nothing on the site itself tells you that. It just looks exactly like it did yesterday.

So when an update doesnt show up, dont assume your friend’s browser is being weird. Check the deploy first. On Vercel that’s your project’s Deployments page, where each deploy says whether it worked or failed, and the failed ones have logs showing which line broke the build. Hand that error to your agent and it knows exactly where to look.

How Orbit helps

In Orbit, the program I built to run my agents, projects on Vercel get a little deploy health dot right on the project… live, failed or building. Click it and you get the deploy logs and a snippet of what went wrong, plus an option to have Apollo, Orbit’s built in assistant, draft a fix that you look over before anything gets queued. Orbit is in Alpha and free right now if you wanna try it: https://orbitdev.app

The rest of these words, like React and Next.js, are in the Learning Atlas if you want to go deeper.

What did you use for your first deploy? I’m curious what’s been easiest for folks just getting started.