Deploy means taking the finished version of your site or app and putting it onto a live host where the public can reach it. It is the moment your work moves from a private preview to a real address. Modern tools deploy automatically whenever you save changes, so it is often one click or none.
Information current as at 5 July 2026
Deploy is one of those words that gets used constantly and explained never. It sounds like a big technical event. It is actually a simple idea, and once it clicks, a lot of the launch process stops feeling like magic.
Deploying is publishing. You have a version of your site that works; deploying is the act of copying it onto the always-on host so that anyone with the address can use it. Before you deploy, your work lives in a private space only you can see. After you deploy, it lives at a public address. That is the whole idea. The reason it has its own intimidating word is that, behind the scenes, a few steps happen automatically to package and place your files, but conceptually it is just the moment you press publish.
Most modern sites go through two steps: a build, then a deploy. The build takes the code you (or the AI) wrote and turns it into the optimised, packaged files a browser can load quickly, compressing things and bundling them together. The deploy then places those built files on the host. When a tool says "building" and then "deploying", that is the two steps in sequence. If a deploy fails, the error is very often in the build step, meaning something in the code stopped it packaging cleanly, which is a different and more fixable problem than the site being down.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
The reason deploying feels invisible on modern tools is continuous deployment: the host watches your code, and every time you save a change, it automatically rebuilds and redeploys the live site. You change a headline, the site updates itself a minute later. This is wonderful for speed but worth understanding, because it means a careless change goes live immediately, and there is no separate "publish" gate to catch a mistake. Knowing your saves are going straight to the public changes how carefully you treat them, especially once real customers are relying on the site.
A confusing situation: the tool says the deploy succeeded, but the live site is broken or blank. This usually means the packaging worked but the running app hit a problem the build could not see, most often a missing setting. The classic cause is an environment variable, a secret like a database key, that exists in your preview but was never added to the live host, so the live app cannot connect to anything. A successful deploy only promises the files arrived; it does not promise the app has everything it needs to run. That gap is where a lot of "works in preview, not live" mysteries hide.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
Whether you can name exactly what you want built, or you just know something is leaking, the next step is the same conversation.