0042. A static public site on the apex domain serves the landing page, pricing, legal pages, and the docs
- Status: Accepted; its “One environment” rule is to be superseded by 0052 (Proposed)
- Date: 2026-11-18
Context
Section titled “Context”- The managed service needs a public website before it can send real mail: Amazon SES reviews a production-access request against the sender’s website, and expects to find what the service does, its terms, its privacy policy, its acceptable use policy, and a contact for abuse.
- The app domain serves the API and the dashboard, and routes every path the API does not own to the dashboard SPA (ADR 0028). It has no room for marketing or legal pages, and they need no sign-in.
- The documentation is public and lives in
docs/(ADR 0002).docs/llms.txtanddocs/api/reference.mdare generated from the action registry (ADR 0031), whose open point is the public URL of the generated docs:llms.txtlinks toapi/reference.mdrelatively, which would resolve under the API’s/api/*ifllms.txtwere served at the app domain’s root. - The managed service adds no fixed cost by default (
docs/architecture.md, Cost model). Workers Static Assets serve files with no script at no extra cost on the Workers plan the service already has (checked 2026-11-18). - The landing page, prices, and legal texts are the managed service’s, not the open-source edition’s: a self-hoster has no use for them, and they name the operator.
Decision
Section titled “Decision”- One public site, on the apex of the product domain. It serves the landing page, pricing, the legal pages (terms of service, privacy policy, acceptable use and anti-spam policy, contact and abuse reporting, and, once the payment and refund terms are decided, a commercial disclosure required in some jurisdictions), the docs under
/docs, andllms.txtat/llms.txt.www.redirects permanently to the apex, keeping the path and query. The app domain (ADR 0028) is unchanged and serves no site page. - Static, built with Astro and Starlight. Starlight renders the docs; the other pages are Astro pages. The site runs no server-side code and sets no cookies.
- Hosted as an assets-only Worker. A Worker of its own with Workers Static Assets and no script, deployed with
wranglerby the operator. Not Cloudflare Pages, so the site uses the same product, tooling, and custom-domain mechanism as the API Worker. It shares nothing with the API Worker: no binding, no route, no secret. - One environment. The site exists only in production. Staging gets no public copy: the site has no backend whose environment it would follow, a second public copy of the legal pages and docs could be indexed and quoted as the real one, and a build is previewed locally before a deploy.
- The site’s code is private; its docs content is public. The site lives in
cloud/site/, which is never synced to the public repository (ADR 0002). The docs stay indocs/as the single source, and the site renders them at build time.docs/cloud/is private and is never rendered. llms.txtis served at the site’s root with absolute links. The site’s build copies the generateddocs/llms.txt, rewrites its links to absolute URLs of the rendered pages underhttps://<apex>/docs/, and gives the endpoint paths it names (such as/mcp) the app origin. The committeddocs/llms.txtkeeps relative links, which resolve in the repository. This resolves ADR 0031’s open point.- Operator values come from the build environment. The domain, the app URL, the legal entity, its address, and the contact and abuse addresses are build-time environment variables, never committed. The build fails if one is missing. Plan values are configuration, rendered on the pricing page with the scenario and the check date that ADR 0014 requires for every comparison.
Consequences
Section titled “Consequences”- The open-source edition has no public site, landing page, or legal pages. Its docs remain readable in the repository, and a self-hoster can publish them with any static site generator.
- A change to
docs/changes the public site at its next deploy. Docs must keep working when rendered: relative links between Markdown files, which the build rewrites to site paths. - The legal texts are drafts until legal review; publishing them is the operator’s decision, not a pull request’s.
- The apex and
www.custom domains, and the redirect, are managed with the rest of the managed service’s Cloudflare resources. - The pricing page reads plan values from the site’s own configuration. When billing in core gets its plan configuration (ADR 0013), the site reads that instead, so the values are kept in one place.
- Open:
- The refund policy, which the terms of service need (
docs/architecture.md, Open decisions). - Whether the site later carries a sign-up flow or waitlist form, which would need a backend.
- The refund policy, which the terms of service need (
Amendment (2026-11-20): the pricing page shows no comparison with competitors, following ADR 0014’s amendment of the same date. The scenario and check date above apply only if that decision changes.