# Edge (/academy/edge)



One headquarters is a long walk.

**Edge** means a copy of a tiny program sits in many cities, and the request goes to the nearest door, not the one you rented in a single region. A [CDN](/academy/cdn) already parks files at those doors. Edge parks a little [worker](/academy/worker) there too.

The work that belongs at the door:

* Are they signed in, or bounce them.
* This link died; send them to the new one.
* Mobile gets this layout; another locale gets this currency hint.

That is a greeting. It should not cross an ocean.

The work that does not: a fat [database](/academy/database) query, a twenty-second export, a [process](/academy/process) that wants `fs` and a warm Node. Those stay in a region. The door is small on purpose. If you try to run the whole kitchen in the foyer, you will miss APIs the [runtime](/academy/runtime) never packed.

[Latency](/academy/latency) is why this word shows up in the [builder](/builder) and on host dashboards. Distance is time. Judges feel time. They will not read your architecture slide.

[Serverless](/academy/serverless) is the rental. Edge is *where* the rental sits. A Cloudflare Worker and a Vercel middleware are the same instinct: do the first decision close to the person who asked.

At a hackathon, use the door for the hello. Keep Convex, Postgres, and the long jobs in the room that can hold them. create-hackhaton-space-stack already [deploys](/academy/deploy) into hosts that think this way. You just have to stop shipping the entire app to the foyer.

**What this unlocks**

"Run it at the edge" stops sounding like a brag. It means: put the greeting where the guest is standing. Files close ([CDN](/academy/cdn)). Decisions close (edge). Dinner in the kitchen.

The first byte should not need a passport. The pantry still can.