You've changed the website. Nobody can see it until you deploy.
A chef perfects a new dish in the kitchen. Customers can’t order it until the new menu goes up in the window.
Deploying is putting up the new menu. It’s the step that takes a new version of a website or app and makes it live for real users.
What happens in a deploy
- the latest version is built into its finished form
- it's copied to the servers
- visitors start getting the new version instead of the old one
On a modern website, this can take under a minute, often with a single command.
Small and often
Teams used to deploy a few times a year, in big risky launches. Most now deploy small changes often, sometimes many times a day. Small changes are easier to check and easier to undo.
What it isn’t
It isn’t the same as finishing the work. A deploy is just the moment it goes live. Often it first goes to a test copy called staging.
Where the comparison breaks down
Changing a menu is instant and harmless. A bad deploy can break a website for everyone, which is why teams have a quick way to roll back.
How the words fit together
You test on staging, then deploy to production. CI/CD can deploy automatically. Rollback undoes a bad one.
Many teams avoid deploying on Friday afternoons. If something breaks, nobody wants to fix it over the weekend.
When you'll hear it
“We deploy every day.” New changes go live daily, in small steps.
“The deploy failed.” Something went wrong while putting the new version live, so the old one is still running.
“It's deployed to staging.” The new version is live on the test copy, not the real site yet.
“If a deploy goes wrong, how quickly can we put the old version back?”


