Naven
Glossary
Edge computing
Running code in many small locations near users instead of one big data centre.
A request to a server three thousand miles away spends most of its time travelling. Edge platforms put the code in hundreds of cities and route each request to the nearest one, which removes that travel for everything that does not need a central database.
The trade is that edge code is constrained: short-lived, memory-limited, and awkward for anything that needs a lot of state.
Where Naven stands
Naven's whole server is one edge worker, which is why the site and the API answer from the same place and why there is no CORS layer between them.