Deployment · Hosting
Deployment / Hosting
What is deployment?
- Deployment = put it on a server and run it
- Hosting = renting space that stays up 24/7
- Releasing what you built to the world
The moment you deploy code, the nature of the result changes. When it runs on your own laptop, you are the only one who sees an error. Once an address is issued, everyone who visits sees it. Deployment is not the completion of a feature; it is the start of accountability. Who can access it, how many users it takes to slow it down, who notices when the server stops at 3 a.m. — every one of these questions only appears after deployment. That is why, when someone at your company reports “it’s all built,” the next question should be “what’s the URL?”
Hosting depends on what you are putting online. A static site that runs on just HTML, CSS, and JavaScript is well served by the free tiers of Netlify, Vercel, or GitHub Pages, and connecting an HTTPS certificate and a domain takes a few clicks. Once login, payments, or data storage are added, you need a server and a database, so you move to Firebase, cloud run services, or AWS, and the model becomes pay for what you use. One more point: in practice, you never have just one environment. You keep a test (staging) environment separate from production and set up in advance a rollback path to the previous version in case something goes wrong.
The most common mistake we see is the belief that “if you don’t know the link, you can’t get in.” Search engines find deployed addresses on their own, and API keys written into frontend code can be read as-is in the browser’s developer tools. A supplier price list uploaded as an “internal demo” turns up in search results, or a leaked key lets someone else call APIs on your account and run up charges. Both really happen. Even free plans start charging once you exceed the traffic limit, so before you press the deploy button, set up access restrictions, separate your keys, and turn on usage alerts.
Jaryong KooMarketing PhD and authority in AI, data analytics, and personal branding
John KimAuthor of B2B Marketing Design and CEO of Nanum Consulting“Deployment” — putting software into the user’s environment — has long been the final stage of development, and it has become automated and simpler as cloud and hosting services have matured.
Consider a hypothetical case. At Company A, an auto parts maker with 140 employees, six production planning staff who had finished vibe coding training built a web app for looking up customer delivery dates. Three weeks later, the app still ran only on Manager Kim’s laptop, and the sales team was still taking 40–50 delivery-date calls a day.
- It began when Lee, the IT manager, asked, “Why hasn’t that been handed over to us yet?” All that Manager Kim had shared was a single screen-recording video, with no address to access at all.
- When Lee opened the code, three access keys to the company ERP and a shared-folder path were written right there in the source. Moving those keys into environment variables alone took two days.
- Deciding that a static page used only for lookups needed no separate server, they created a GitHub repository and connected it to Vercel’s free tier. It took under 20 minutes from the first deployment to a live URL.
- The suggestion that “people who know the link can just use it” was set aside. Because the screen shows delivery dates and unit prices together, they added company-account login and search-engine indexing blocks, plus a monthly traffic alert.
- Two weeks after the rollout to the floor, delivery-date inquiry calls fell from 40–50 a day to 12, and the app averaged 180 visits a day. The tally showed sales team response time down by about 9 hours a week.