Build log
ChaseOS Web: making Early Access a technical boundary
How the ChaseOS front door exposes a real waitlist and product story while keeping downloads, checkout, admin export and managed-agent claims behind explicit gates.
Source: ChaseOS Web repository README, route/configuration surfaces and public chaseos.ai deployment (privacy-screened)
Context#
A governance-first product is unusually easy to misrepresent on a marketing site. The interesting features are often the boundaries: which surfaces are genuinely live, which are previews, and which actions the public deployment must refuse. ChaseOS Web treats those distinctions as implementation state rather than footer disclaimers.
Static story, narrow dynamic edge#
The public shell is a Vite/React application deployed through Cloudflare Pages. Dynamic behaviour is deliberately narrow: Pages Functions handle the edges that need server authority, while the waitlist uses Turnstile verification and D1 storage. Ordinary local builds and smoke tests do not need Cloudflare, credentials, DNS or production data.
Disabled means disabled#
The public admin route is a stub, not a hidden control panel. Export requires an explicit enable flag, the correct storage mode, authorization and an approved database binding. Downloads, marketplace payments and managed agents remain blocked. The page copy and the backend gates describe the same state, which prevents a marketing promise from quietly getting ahead of the system.
Route boundaries are product boundaries#
Studio, Forge, standards, pricing, docs, security, roadmap and support each have a public route, but the existence of a route is not treated as proof that every underlying service ships. The website can explain a product surface, collect interest or expose reviewed metadata without implying an installer, transaction path or managed runtime exists.
Current boundary#
ChaseOS Web is live on chaseos.ai as an Early Access website with a verified waitlist path. It is not a public installer, live marketplace checkout or managed-agent service. The next proof for each gated surface must come from its own implementation and acceptance evidence before the website promotes it from preview to live.