Where Does a Website Actually Run?

Where does a website live?

A website is ultimately just a collection of files — HTML, images, and so on. Those files are stored on a computer called a "server," managed by someone. When you open a URL, your browser fetches those files from the server and displays them on screen.

So where is that server? There are four main options, each with its own strengths and weaknesses.

4 hosting options

Fig. 1: 4 options plus free static publishing. Teens should start with free GitHub Pages and upgrade as needed.

What makes each option special

① Home server: Run your PC 24/7 and use it as a server. Totally free to configure, but power outages and security attacks are real risks — not recommended for beginners.

② Shared hosting: Many users share one server. Monthly fees start at a few hundred yen. The standard choice for starting a WordPress blog (Sakura Internet, Xserver, Lolipop, etc.).

③ VPS (Virtual Private Server): One physical server is split into virtual slices; you get your own slice. You can configure the OS, making it developer-friendly (Sakura VPS, ConoHa, etc.).

④ Cloud: Pay for what you use — costs scale up and down with demand (AWS, Azure, Google Cloud). Used by international services and apps with wildly varying traffic. Watch out: misconfiguration can lead to unexpected bills, so always set a budget alert first.

Data centers behind the scenes

Shared hosting, VPS, and cloud services all ultimately run inside huge buildings called "data centers." Telecom companies and cloud providers operate these facilities with robust power, cooling, networking, and around-the-clock monitoring. As a user you rarely think about the physical location, but behind your screen there are real machines and real people keeping everything running.

How to choose

For a personal bio page or a club website, GitHub Pages or shared hosting is usually enough. For a WordPress blog, go with shared hosting. If you want to study Linux or deploy your own apps, try a VPS. If your app needs to handle wildly varying traffic or combines many services, consider the cloud. Start with the smallest option that matches your goal — it keeps costs and management burden low.

Fig. 2: Every data center needs all 8 facilities. Construction cost per building: ¥10–50 billion. This is what runs behind every website.

Common pitfalls

3 things beginners often run into

Shared hosting is cheap but limited. If you later want AI features or real-time communication, you'll need to migrate to a VPS or cloud.
Cloud is billed by usage. A misconfiguration can lead to unexpectedly high charges.
Thinking you can stay within the free tier forever — limits and conditions can catch you off guard. Set a billing alert before you start.

How does this help your future?

The experience of publishing your own site to the world is a powerful entry point into web and cloud learning. Professionals who can build and operate servers and cloud infrastructure work as cloud engineers and DevOps engineers, among other roles. Start small, and work toward being able to explain the whole setup in your own words.

Things you can try today

3 steps to publish your first site

Create a GitHub account and upload an HTML file to a repository
Go to Settings → Pages and enable publishing — within minutes a username.github.io URL is ready
Send the URL to a friend and ask them to confirm they can access it

Summary

A website runs inside someone's computer (a server), which ultimately lives in a data center somewhere in the world. If you know the differences between shared hosting, VPS, and cloud, you can pick the right home for your project. Start with a small free option like GitHub Pages and move up as your needs grow.

Check Where does a homepage actually run?