advice accepted goes to: this-edition E explorer
Ship now, and ship your startup serverless: no servers of yours, no database, client side, with privacy by design and control of your agents
A founder with no servers has nothing to run at three in the morning and nothing to pay for when nobody is using it; 'if it bills you by the hour when nobody is using it, it is not serverless'. SG/Send and sgit give data encrypted on the user's device on a server that cannot read it; RiskMandate's techniques control the agents the company runs on. You ship, it is painful, and if they do not miss it you try again.
Decided by. Dinis, in Gen ZX Developers, adopted as the frame of rc2 (decision 015)
Note. No server is the product, not a preference: with no server the company never sees the audio, which removes at a stroke data custody and its governance, a place for a breach, a shared key an abuser could drain, key management, a billing system, a database of users, a thing that has to scale, a single point of failure, and a thing that has to be up at three in the morning with a person to wake. Add a server and every item comes back at once, not gradually: 'a different company, with a different cost base and a different risk register'. The commit history (239 commits and 27 releases in three weeks) is what moving fast looks like, and 'the complexity of the moving parts is what decides how fast you can move'.
Where it comes from
- Gen ZX Developers Ship serverless; The objective: start a company (article)
- No server, by design 'It is no servers of mine with logic in them' (newsroom)
- Ephemeral town planner services the by-the-hour test (newsroom)
- For a startup, the most important question is whether they miss it 'Not to plan, not to pitch, not to architect. Ship.' (newsroom)
- The key is the billing system Why no server is the product (newsroom)
What it answers in the 2018 book
- Serverless answered outline, Concepts
Where it goes
Chapter Serverless, for real, part Build it without a server (drafting); topic Building blocks: cloud, serverless, free models, git and CI.
Other ideas proposed for the same chapter: Building blocks: cloud as Lego, free models with your own key, git as a standard, The file system is the database: load, extract, transform, save, and keep every intermediate as a file, No server, by design: retire the back end too, and keep only commodity servers, What serverless costs when nobody is using it, product by product, 18 October 2026, The name shows the glue: a first version is often a villager's work dressed as a town planner's, Move the cloud, not the code: a twin the application cannot tell from the real service.
Node idea:ship-now-ship-serverless in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.