Naven
Glossary
Serverless
Running code without managing a server — the platform starts it on demand and bills for what it uses.
The name is inaccurate and has stuck. There are servers; you simply do not provision, patch or scale them. Code is deployed as functions that the platform starts when a request arrives and stops when it is idle.
The benefits are operational: no capacity planning, no idle cost, and scaling that happens without anybody being paged. The constraints are real — short execution limits, limited memory, and a cold start when nothing has run recently.
Where Naven stands
Naven's entire server is one serverless worker at the edge, which is why it serves the site and the API from the same origin and why there is no infrastructure to maintain.