Family OS brings cameras, climate, energy, lighting, security, and the family's whole schedule into one calm control center — running entirely on hardware you own. No cloud account. No data leaving the house. Just one place that runs the home.
Most homes accumulate a dozen apps, a junk drawer of remotes, and a different login for every device. Family OS replaces all of it with a single system you actually control.
Ten apps and a pile of remotes become a single, consistent interface — on the kitchen wall, your phone, or any browser on the network. Every module looks and works the same way.
There's no cloud to sign into. Family OS runs on a computer in your home and keeps every byte of your family's data right there. You own the box, so you own the data.
House Modes coordinate every system at once. Tap Away and the lights drop, the alarm arms, the climate sets back, and the house settles — in a single move, not twenty taps.
Every screen below is the running application — clean, fast, and built to live on a wall display all day. Click through a few.
The home dashboard — your whole day and house at a glance.
Home, Away, Night, Vacation. Each mode reaches across lighting, climate, security, media, and shades and sets them all together — so the house responds to your day instead of waiting for you to manage it.
Live consumption, solar production, battery state, and per-circuit load in one readable view — so the most complex system in the house is also the easiest to understand at a glance.
Cameras, sensors, locks, and access roll up into one monitoring view, with a live activity stream and alerts that actually mean something. Arm it yourself, watch the feeds, or hand it to House Modes.
Family OS models the entire surface of a connected home — from the grocery list to the generator — as a catalog of modules that all share the same design and the same architecture. Adding the next one is a known quantity, never a rewrite.
Dashboard, Control, Wall kiosk, Assistant, Automations, Modes, Rooms, Briefing, Analytics, Alerts, Activity.
Alarm & sensors, Ring cameras, face & plate recognition, guest access, perimeter, gates.
Life-safety shutoffs, panic & emergency, shelter life-support, escape routing.
Thermostats, air & water systems, heated floors, pool chemistry, spa, fireplaces.
Lights, shades, shutters, whole-home audio, theater, intercom, elevator, vacuums.
Garden, irrigation, mowers, energy & generator, water levels, weather, network.
Vehicles, aviation, waterfront, lab, finance, and the cellar — tracked the same way.
Calendar, tasks & chores, meals, shopping, routines, allowance, health, pets, notes, documents, vault.
Pantry, packages, supplies & auto-reorder, laundry, upkeep & maintenance log.
The hard part of a home hub isn't any one feature — it's keeping 75 of them coherent. Family OS does it with one repeatable pattern: every device type talks to a small provider interface, so a real backend drops in at a single seam without touching a line of UI.
Each device type implements a provider interface. A file-backed mock runs today; a real integration — Hue, Sonos, Home Assistant, an alarm panel — drops in by changing what getLightsProvider() returns. No route or component changes.
TypeScript everywhere, Zod-validated at every storage boundary. State is versioned JSON on disk — readable, easy to back up, with no database to operate or migrate.
types → storage → API → page → components, built the same way every time. 75 modules, one mental model — which is exactly why the catalog can keep growing.
// The control surface every lighting backend implements. // UI and API only ever talk to this interface — so swapping // the mock for Hue/Home Assistant is a one-line change below. export interface LightsProvider { readonly id: string; listLights(): Promise<Light[]>; getLight(id: string): Promise<Light | null>; setState(id: string, patch: LightStatePatch): Promise<Light | null>; } // Resolve the active provider. Branch here on a stored // config value when real hardware is wired up. export function getLightsProvider(): LightsProvider { return mockLightsProvider; }
// Designed and built by Thomas Sprayberry — Sprayberry Labs.
Family OS has no cloud, no account, and no third party in the middle. It installs on a computer you control and keeps cameras, schedules, and everything else on that machine — so there's nothing to breach, no vendor to trust, and nothing to cancel.
Happy to walk through the live system, the architecture, or the code — whichever's useful. Family OS is a Sprayberry Labs project, built and run in-house.