# Server (/academy/server)



Shut your laptop lid. It sleeps. A **server** does the opposite.

Plugged in. Online. Awake. Often in a building you will never visit, in a rack with a thousand cousins, answering requests around the clock. No screen you stare at. No keyboard anyone types on. It just waits to be asked.

**Server** is doing what it sounds like: it *serves*. You are the customer. It is the waiter who never clocks out.

Every time someone hits your URL after [deploy](/academy/deploy), the same three beats:

1. The browser sends a request. "I want the page at this address."
2. Somewhere, a server hears it, finds what was asked for, packages it.
3. It sends that back. The browser paints it.

That round trip is a blink. It happens millions of times a day for apps you never think about.

Back to the restaurant. The [frontend](/academy/frontend-backend) is the dining room. The [backend](/academy/frontend-backend) is the kitchen. The [database](/academy/database) is the cabinet. The **server** is the building they all rent — the power, the floor, the door that stays unlocked at 3 a.m.

A [backend](/academy/frontend-backend) is software. A server is the box it runs on. People mash those together. Keep them apart. When someone says "the server is down," they mean the kitchen went dark. The waiter went home. Everyone at the door gets a blank plate.

**Two things that surprise people**

* **The [cloud](/academy/cloud) is not magic.** It is someone else's servers. Save a file "to the cloud" and it landed on a machine that probably belongs to Amazon or Google, in a warehouse with a hum you cannot hear. Marketing says fluffy. Reality says racks.

* **One server can pretend to be many, and many can pretend to be one.** Big apps spread across hundreds of boxes so one overheating fan does not take Instagram offline. Your hackathon demo probably runs on one. That is fine until the demo is the product.

**The serverless twist**

You will hear [serverless](/academy/serverless) constantly. The name is a little bit of a lie. There is still a server. You just do not own it, name it, or babysit it at 3 a.m.

Vercel, Cloudflare, Convex — they keep a pool of machines awake for everybody. Your app borrows one for the half-second it is needed, then lets it go. Same as calling a ride instead of owning the car. The car still exists. You are not the one parking it.

At a hackathon the server is usually rented by the moment or hidden behind a deploy button. You still have one. [Localhost](/academy/localhost) is rehearsal — the show runs on your laptop, audience of one. The server is opening night — the show runs while your lid is closed.

Your laptop sleeps. A server does not.