What does deploy mean — and how it differs from “it works on my machine”

Here's the moment that trips up every beginner. You built an app, it opens in your browser at something like localhost:3000, every click works. Looks done — time to show the world. You send a friend the link — and it doesn't open for them. Why? Because "works for me" and "works for everyone" are two different things. The bridge between them is called deploy.

What it is

To deploy means to move your app from your computer to a server that's reachable from the internet around the clock. While the app lives only on your machine, only you see it. After deploy it lives "outside" and runs even when your laptop is closed.

An analogy: while you cook a dish in your own kitchen, only you get to taste it. Deploy is opening a café: the same dish, but now anyone can come for it, and the kitchen runs without you standing there.

Why "localhost" is just you

When you run a project, it starts on your computer, and the address localhost literally means "this very machine." A friend visiting that address lands on their computer, not yours. On top of that your laptop isn't on 24/7 and hides behind a home router — there's no reaching it from outside.

A server solves both: it's always on, it has a permanent internet address, and anyone can open it from anywhere. Deploy is the process of sending your code to such a server.

How it usually goes

You don't need to wire up a server by hand — there are platforms that do almost everything for you. In broad strokes:

• You upload your code (usually through a connected GitHub repo).
• The platform builds the app and runs it on its server.
• You enter your environment variables — the keys and addresses you can't keep in the code.
• In return you get a public link you can actually send to anyone.

Then the nice magic kicks in: on every code update the platform rebuilds and ships the new version itself. Step by step, see the guide how to deploy your app.

Why it matters to you

Without deploy, your project is a rehearsal in an empty hall. You can't share it, can't show it in an interview, can't invite first users. Deploy is the moment the thing becomes real: there's a link you can send.

And one important detail: what worked locally sometimes breaks after deploy — a forgotten environment variable, a different database address, a missing file. That's normal and fixable. Knowing deploy is "a move to another environment," you don't panic at the first red error — you go check what's actually different on the server.

Where you'll meet it first

Probably when you want to show off your first project. The most beginner-friendly platforms for sites are Vercel and Netlify: connect a repo, hit "Deploy," and a minute later you have a working link. For apps with a server there's Railway and friends. The first successful deploy is its own little joy: there it is — your address on the big internet.

Question: is deploy the same as hosting?

Almost, but not quite. Hosting is the place where the app lives (the server). Deploy is the action: the process of delivering your code to that hosting and starting it. Hosting is where, deploy is how you get there. In practice, platforms give you both at once.

Question: do I redeploy after every change?

Technically yes — but not by hand. Platforms support automatic deploy: you just push new code to the repo, and they rebuild and ship the update themselves. Set up the GitHub link once, and deploy happens on its own with every push.