Everyday · architecture profile
MAX
A connected companion for an existing walker. An Astro web app on Cloudflare plus a local simulator, a device service and shared protocol packages. The hardware is a prototype.
How it is built.
MAX is a workspace rather than a single app: a public Astro site, an owner PWA, a software simulator, a device-side service, and shared protocol and SDK packages. The hosted surface runs on a Cloudflare Worker with D1 and R2. The physical walker is a prototype, and the product pages say so.
- Stack
- Astro 7 web app, React, TypeScript, pnpm workspaceEvidence: apps/web/package.json; pnpm-workspace.yaml
- Runtime
- Worker `max-web` for the SSR site and PWA; a separate `max-gateway` Worker is configured with a Durable Object but its README claims no deployment; local Docker Compose runs the gateway and device simulatorEvidence: apps/web/wrangler.jsonc; apps/gateway/wrangler.jsonc; apps/gateway/README.md; compose.yaml
- Storage
- D1 `max-db-prod` and R2 `max-media-prod`; gateway device state would live in the MAX_DEVICE Durable ObjectEvidence: apps/web/wrangler.jsonc; apps/gateway/wrangler.jsonc
- Identity
- Email magic-link sessions with household roles and a platform-admin flag; the public demo needs no account.Evidence: apps/web/src/lib/auth.ts; apps/web/src/pages/api/auth/request.ts
- Delivery
- max.loftwah.com for the web app through `pnpm deploy`; the gateway has no deployment scriptEvidence: apps/web/package.json; apps/gateway/README.md
- Integrations
- Resend for auth and lead email; Cloudflare Turnstile on forms; OpenAI transcription only in the local stack; ElevenLabs only in authoring scriptsEvidence: apps/web/src/lib/lead-capture.ts; apps/web/src/pages/api/max/voice.ts; scripts/audio/README.md
The shape of the system.
- Public siteAstro pages explain the concept, the prototype status and the owner app.Evidence: apps/web/src/pages
- Owner appThe installed shortcut opens the owner route; a magic-link session is required.Evidence: apps/web/src/pages/api/auth
- maxdThe device-side service owns FIND and STOP behaviour during local stack runs.Evidence: apps/maxd; README.md
- GatewayA configured Worker would hold device state in the MAX_DEVICE Durable Object. Its README says no gateway deployment is claimed, so the atlas marks it planned rather than live.Evidence: apps/gateway/wrangler.jsonc; apps/gateway/README.md
- max-simA software simulator stands in for the walker. The demo observes adapter state rather than animating an optimistic browser result.Evidence: apps/max-sim; README.md
- Protocol and SDKShared packages keep the web app and device service on one contract.Evidence: packages/protocol; packages/max-sdk
One product, two runtimes, and a simulator that says it is one.
MAX is the only product in this catalogue that has to be honest about two kinds of existence at once: a hosted software product that anyone can open, and a physical companion that does not yet exist outside a prototype.
The workspace keeps those apart. The Astro app owns the public story, the owner PWA and the magic-link session. The simulator and the device service run locally, with a shared protocol package defining what FIND and STOP mean. The demo observes the adapter's state instead of animating a success it did not receive, which is the difference between showing a concept and faking a device.
That structure also makes the review boundary clear. The web deployment can be checked from outside; the hardware cannot. Saying so on the architecture page is not a disclaimer bolted onto a finished product — it describes which half of the system has actually been built.
Engineering decisions worth knowing.
- The simulator is labelled, not hidden
A software demo is useful before hardware exists only if nobody mistakes it for a device. The adapter boundary keeps the simulation honest and gives the real device the same interface later.
- One workspace, separate runtimes
Web, device service and simulator share contracts but not a deployment. A hosted outage does not stop a local stack from running.
What it connects to.
No verified cross-project runtime relationship. MAX is reachable from Woodhouse as a published record, and its product links are ordinary navigable links.
Authoritative public sources
What this review does not know.
- No physical walker was available for this review, so fit, battery, safety and real FIND/STOP behaviour are unverified.
- The gateway Worker is configured but its README claims no deployment; device state over the network is therefore planned, not live.
- Whether either speech provider is configured in the live web deployment was not verified; OpenAI is described as local-stack only and ElevenLabs as authoring tooling.
- Installer signing and OS coverage were not checked.