Hosting is renting space on an always-on computer that serves your website to anyone who visits. Your own laptop cannot do this: it sleeps, moves, and is not built to take traffic. A host keeps your site running around the clock at a fixed address, so visitors reach it whether or not your machine is on.
Information current as at 5 July 2026
Hosting sounds technical, but the idea is ordinary. A website is just files. Those files have to live on a computer that is always on, always connected, and always ready to hand them to a visitor. That rented computer is your host. Everything else is detail.
When your AI builder shows your site in a preview, it is running on the builder's machines, not yours. To be truly live, the files need to sit somewhere that never sleeps and can answer thousands of visitors at once. Your laptop closes its lid, joins different wifi networks, and has no fixed public address, so it cannot be that place. A host is a computer in a data centre that does nothing but stay on and serve files. You rent a slice of it and, in return, your site is reachable at any hour from anywhere.
There are two broad kinds, and knowing which you need saves money and confusion. Static hosting serves fixed files: pages, images, styling. It is fast, cheap, often free at small scale, and perfect for a brochure site, a landing page or a portfolio. App hosting runs code and talks to a database: it is what you need if your site has logins, saves data, takes payments or personalises what each user sees. Many AI builders produce apps that quietly need the second kind, which is why a site that looked simple sometimes needs more than a static host to run properly.
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 popular hosts offer generous free tiers, and for a new project they are genuinely enough. They typically cover a custom domain, automatic HTTPS, and enough bandwidth for early traffic. Where they stop is usually volume and features: heavy traffic, always-on background jobs, or bigger databases push you onto a paid plan. That is a good problem, because by then the site is working hard enough to justify it. Start free, watch for the limits the host warns you about, and upgrade only when real usage asks for it, not before.
The signals are practical, not technical. Your site slows down under traffic. You hit a bandwidth or usage cap and the host emails you. You need something the free tier will not do, like a proper database, scheduled tasks, or higher limits on how much your app can process. None of these mean you did anything wrong; they mean the thing you built is being used. At that point the decision is whether to keep bolting on plans or to have the whole setup put on a proper footing, which is a sensible moment to get a second opinion.
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.