Reedster's Home Tech

Design mockups for the two software surfaces behind the home service: the app a household sees, and the console we run the fleet from. Static HTML, no code behind it yet. Click through and tell us what feels wrong.

The household app

Lives on the client's phone. One job: prove the monthly care plan is doing something, in plain words, with nothing for them to do.

Home The report card. Green means relax. Amber means we found something and we're already on it. Includes the backup proof card and the app launcher. Status What's happening at home right now: doors and locks (open reads amber), the lights that are on, and a plain event feed from the door, motion, and light sensors. Activity What we did for you: every update, checkup, and quiet fix as a plain sentence with a date. The subscription made visible. Help One phone number, a short note form that attaches the health report automatically, and honest support hours. Web app The same household app in a desktop browser. One responsive web app, not a second product: the phone view stacks, the laptop view fans the services into a bento grid with the proof and care plan alongside.

The operator console (fleetd)

Internal. Every household on one screen, staged updates that go lab first, and an onboarding checklist that makes installs repeatable.

Fleet All households: health, backup age, last verified restore, rollout ring, open alerts with remediation state. Alerts Classified incidents: internet blips and power cuts resolve themselves, area outages group into one line, and capacity forecasts read as sales conversations. Household detail One home's modules and version pins, backup posture, drift check, remediation policy, and the audit log. Rollouts Updates flow lab to canary to fleet with soak windows and health gates. Majors stop for a human. No blind auto-updates. Onboarding Paperwork, bench provisioning, burn-in countdown, install day steps, and the per-client manifest.

The deployment backbone (Gitea)

A separate tool, not part of the operator app. One private Gitea repo per household is the source of truth for their deployment. fleetd and the operator reach it, but it stands on its own.

Repository Each household is one private Gitea repo. Digest-pinned compose, the manifest, per-house data. Branches are rollout rings, commits are deploy history, Renovate PRs are the update gate.

Reedster's Home Tech · Reed LLC · Massillon, Ohio. These are design previews, not a live product.