Shipping & Running
$defineedge--plain-english
TLDRRunning code near the user instead of in one faraway basement.
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 already parks files at those doors. Edge parks a little worker there too.
The work that belongs at the door:
That is a greeting. It should not cross an ocean.
The work that does not: a fat database query, a twenty-second export, a 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 never packed.
Latency is why this word shows up in the builder and on host dashboards. Distance is time. Judges feel time. They will not read your architecture slide.
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 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). Decisions close (edge). Dinner in the kitchen.
The first byte should not need a passport. The pantry still can.
