The rooms are always on in cloud hosting. The work that happens while nobody is watching runs from one server. Nothing anywhere depends on a person being signed in.
1 · Always on — no machine of ours
Vercel · Railway · Cloudflare Pages. Nothing user-facing is served from a box we run.
Where the work is asked for and where the answer lands.
2 · The muscle — one server, automation only
A single Hetzner box. Cron wakes every few minutes, each runner checks its queue, and exits immediately when there is nothing to do — an idle tick is free.
Terminal, LP Flow, Podcast and DealFlow have no background work here at all — they are entirely self-contained in their hosting.
3 · Whose credential does the work run on
Each app's own API key — never a person's login. A runner that cannot find its key stops, rather than quietly falling back to whoever happens to be signed in on the box. That matters because the alternative fails invisibly: the work keeps happening and looks healthy, while it is billed to a person and dies the moment they sign out, switch accounts or leave.
What breaks when something goes away
No app and no job has ever depended on a personal machine.
Nothing stopsAgent sessions run on app keys, so no person is in the path.
Nothing stopsEvery room stays up and nobody is logged out. Quill stops researching, distilling and ingesting; Ford stops draining intake.
Automation stopsThe affected room goes down, and any runner that writes into it has nowhere to put its result.
That room stopsslwdev is the fleet's single point of failure for automation only, never for availability. That is a deliberate trade — one box is cheap and simple — but worth knowing rather than discovering. Moving the runners into their apps' own hosting would remove the last machine dependency; not scoped, and the cost of the move is real.