I bought a house and built it an operating system
Behind the build: Home OS, the app that knows my house better than I do.
For years I owned a condo, which is to say I owned the air inside a box. When something broke, the building handled it. My entire maintenance responsibility was one water heater and whatever plumbing lived behind my own drywall. One machine. I felt very on top of things.
Then we bought a house.
The inspection report was 64 pages. Somewhere around page 30 I stopped reading it as a document and started reading it as a cast list. Two air conditioning condensers, one of which, I would later learn from its own nameplate, was built in 1995 and runs on refrigerant the EPA started phasing out while I was in school. A furnace with an electronic air cleaner bolted to it, a humidifier bolted to that, and a little condensate pump underneath, four machines in a trench coat pretending to be one. Two water heaters. A radon fan. Fire sprinklers. A central vacuum system from 1998. An irrigation controller in the basement wired to sprinkler heads I still haven't fully counted. An attic. A french drain.
And in the backyard, mounted on the house, a gray metal box that I confidently told my wife was the awning motor. Reader, we do not have an awning. Three weeks later I opened it and found a transformer for low-voltage landscape lighting, with a mechanical timer and paperwork from the manufacturer still folded inside. I have yet to locate the landscape lights. The box is in the app now, filed under "function to confirm," which is the most honest sentence I've ever written in a database.
That was the moment, honestly. Not the furnace, the mystery box. The house knew things about itself that I didn't, and the knowledge was scattered across a PDF, a drawer of manuals the previous owners left (bless them, thirty years of manuals, including one for a dryer that predates Google), a dozen appliance nameplates in dark corners, and my own text messages. There was no single place that knew the house.
So I did what I always do when a problem scares me a little. I built something.
There's more to the story.
The label safari behind the fridge, the Cloudflare Worker that syncs the whole house in under a second, and the day I gave it a brain. Drop your email and read on. I send new build logs when they ship, and nothing else. No spam, unsubscribe anytime.
no thanks, just let me read →The unglamorous part nobody puts in a demo
Before writing any code that mattered, I walked every room with a notepad and counted things like a census taker. Outlets, switches, floor vents, phone jacks that connect to nothing. Fourteen floor vents on the first floor, if you're wondering. I hand-drew a map of each level on dot-grid paper at the kitchen counter, and they are not good maps, but they are mine.
That sketch became the app's isometric floor plan. Tap a room, see its photos, its paint notes, which machines live there, and what maintenance is due in it. The app politely calls the layout "approximate." My wife calls it "mostly the house."
Then came the label safari. Around 290 photos: every nameplate, every rating plate, every handwritten date a plumber ever Sharpied onto a tank. I crawled behind the fridge with a flashlight for a model number. This is how I learned our older AC unit is a 1995 Carrier, that the water heaters have serial numbers I can now recite to a repair tech over the phone, and that the trash compactor takes a specific bag whose part number was superseded in 2011. Is that useful? It was the day I needed bags.
What it actually is
Home OS is a private web app that lives at its own domain, behind a passcode. There's a dashboard with what's due this week, a maintenance list that knows New England seasons, the floor map, a systems page with every machine's age tracked against its expected lifespan, vendors with our actual account numbers, a document vault with real links to real manuals, and a notes board so my wife and I stop losing house facts in our text history.
Under the hood it's deliberately boring: one Cloudflare Worker, one Durable Object holding a single shared blob of state, WebSockets to push changes between devices. She checks off "replace the furnace filter" in the kitchen and it ticks on my phone in under a second. It installs like a phone app, works offline, and runs on Cloudflare's free tier. There is real comedy in building software with zero maintenance burden to manage a house that is entirely maintenance burden.
Why I gave it a brain
Eventually the app knew more than I could remember, which was the point, but it created a new problem: finding things meant knowing where I'd filed them.
So I added a chat. It's called Ask the House, and the first version was useless in a way that felt very familiar. I asked what filter the furnace takes and it told me to check the manual. It gave me "did you read the documentation?" vibes.
The fix changed how I think about the whole app. Every question now ships with a live snapshot of everything the app knows, every machine, vendor, task, document, and note, rebuilt at the moment you ask. It can open the manuals we've linked and read them. And it's instructed to answer like a decisive friend instead of a liability lawyer: the exact part, a link to buy it, and a tip I didn't ask for but needed, like "buy a few and change it every 90 days, your blower will thank you."
The best part is that it learns for free. There's no training step, no knowledge base to sync. If my wife adds the landscaper to the vendors page, the chat knows the landscaper. When I finally find those landscape lights, I'll write one note in the app and the AI will stop hedging about the mystery box. It runs on Workers AI, on the same Cloudflare account, no API keys, costing approximately nothing.
Where it landed
The house still surprises me. That's fine. That's what houses do. But every surprise now ends the same way: it goes in the app, and the app gets a little smarter, and some future version of me asks a question at 11pm and gets a real answer with a part number in it.
The 1995 condenser is going to die. Maybe this summer, maybe in five years. When it does, I'll know exactly what it was, what it paired with, who to call, and what the rebate looks like. I won't be the guy frantically photographing a nameplate while a repair tech waits on hold.
I like problems you can build your way out of. Homeownership isn't one of them, it turns out. But you can build your way into losing gracefully, and honestly, that's most of adulthood.
— Josh