COFFEE-SAAS holds static HTML product storyboards for the same Coffee Server runtime — dashboards, gateway login, and copy experiments. Same web stack you already met in Module 1; the lesson is not every install should face the public internet. Tiers are UX and policy, not a second engine under the hood.
SAAS1-GATEWAY.html is the workspace setup + login storyboard (with hooks toward /api/workspace/* when wired). It is the front door in the arc: role-based handoff to Teamz, Admin/Biz, Ops, etc. Today much of that is client-side role pick + navigation — the product move is real org auth and a shared session.
The product line contrasts a simpler solo program (honest jargon, short paths, “my Keyman”) with an enterprise / operations program (denser dashboards, quotas, audit language). Same server family; merchandising differs. SERVER3-APPS.html is the heavier “ops launcher” feel; SERVER1-CORE / SERVER2-TERMINAL are additional chrome experiments.
Managing an org eventually requires enforced capability per tier (roles, rate limits, storage policy) on the server — not different business rules copy-pasted into each HTML file.
The arc allows a solo-first story: a serious single-operator experience before multi-account SQL and “Coffee Cloud–class” storage. Team / enterprise can be act two — the same spine grows with you instead of forcing day-one complexity.