Full-Stack Products
ChaseOS Web
The public product website and front door for chaseos.ai.
Outcome
Cloudflare-deployed public site with a Vite/React shell, implemented route map, Stripe-backed subscriptions and credit top-ups, a D1-backed waitlist path, and Early Access boundaries.
Media
Select any frame to enlarge
The homepage in dark mode — the default theme, framing the product as one private command layer over work, memory, agents and execution. The same hero in light mode. Theme preference is saved per visitor. "See it live": real footage of the knowledge graph as an operating surface — runtime profiles (OpenClaw, Codex, Claude Code) parked on nodes, work-beams into the projects they're touching, and a pending-approvals badge rendered live. The same live graph view in light mode. The Studio, Runtime Lanes and Approvals sections, each tagged with its real status (configured, gated, planned) rather than uniform marketing language. The same section in light mode. The account and billing surface: Stripe-backed subscriptions and credit top-ups, live on a Pro account with 10,000 credits available. Name and email redacted for privacy.
Case study
The problem
A governance-first agent OS is a hard thing to explain on a landing page: the product's value is what it refuses to do, and most product sites are structured to promise the opposite. ChaseOS Web has to sell restraint without underselling capability.
Architecture
Vite/React shell deployed on Cloudflare Pages with Pages Functions for the dynamic edges and a D1-backed waitlist path. The route map covers the product story — Studio, Forge, Cloud, developers, pricing, updates — with Early Access boundaries stated per surface rather than buried in a footer.
The content system underneath
Every public surface is driven from a structured content file that carries not just the copy but the operator boundary for that surface — what the page may claim as live, what is gated, and what proof comes next. Marketing copy and governance rules live in the same object, so the site cannot drift into overclaiming without the diff showing it.
Billing, live
Account and billing run on Stripe: real subscriptions (Community, Pro, Studio Max, Studio Plus), a metered credits balance that powers Cloud agent runs and knowledge-graph compute, and a top-up flow for buying credits outside the monthly allowance. This isn't a pricing page describing a future state — it's the account surface an active Pro subscriber sees today.
Where it is now
Live on chaseos.ai behind Cloudflare with a hardening pass documented. Forge, pricing, and Stripe-backed billing are public and working; managed Cloud execution beyond metered credits is still Early Access, and the site says so in its own words.
Verified architecture
System map
Technology
- Vite
- React
- Cloudflare Pages
- Pages Functions
- D1
Scope and boundaries
Not claiming a public installer, live marketplace transactions, or a managed-agent service.