HomeAI
How it works
The landing is the short version. This is the full picture: why now, the household cabinet that keeps your agents from fighting over your devices, the privacy architecture that makes leaks impossible by design, and every question homeowners ask before they trust a home brain.
Why now
Two facts about the homes people live in today — and the deliberate choice HomeAI makes against each.
The trend
Effective March 28, 2025, Amazon stopped supporting the “Do Not Send Voice Recordings” setting — Echo requests that used to stay on-device are now processed in Amazon’s cloud, with no local-only setting left.
SourceAmazon device email to Echo owners; reported by TechCrunch & Ars Technica, Mar 2025
Our move
HomeAI keeps the brain in your house. By default the reasoning that runs your home happens on a box you own — and if you ever turn on an optional cloud AI model, it's your choice and it's disclosed, never the silent default Amazon left you with.
The trend
Most smart devices route every command through a vendor’s cloud — so an outage, a slow server, or a discontinued service can leave your lights, locks, and thermostat unresponsive. Your home shouldn’t depend on someone else’s uptime.
SourceCloud-dependent smart-home gear has repeatedly been stranded by vendor service shutdowns (e.g., Insteon, 2022)
Our move
HomeAI runs on a box in your home. Lights, locks, scenes, and your daily brief keep working even when the internet — or a vendor — goes down.
The household cabinet
Six domain leads each own one slice of the home. Firewalled workers do narrow jobs and only report up. One owner per device — others request, and the Chief of Staff arbitrates. You talk to one brain; behind it, a disciplined org chart where no two agents fight over the same device.
Media can request a scene from Comfort & Climate's Lighting & Scenes — but it never owns the lights.
firewalled workers · sandboxed · each talks only up to its lead, never out
One owner per device — others request; the Chief of Staff arbitrates (a Security “all-on” overrides a Media dim).
Privacy is the floor
Every promise below is paired with the mechanism that makes the opposite impossible — so you’re trusting the design, not our word.
why it can't be otherwisein-memory session
Session memory lives in RAM and is dropped when the conversation ends. There’s no transcript table to leak because nothing is ever written to disk — logs record that a request happened, never what was said.
why it can't be otherwisevault:// pointers
Workers reference secrets as vault:// pointers, never the values. The real credentials stay sealed in the vault and are resolved only at the moment of use — so a log line, a crash dump, or a screen-share shows vault://wifi/guest, not the password.
why it can't be otherwiseoutbound-only
The box and every node connect outbound only — there are no inbound ports to forward, scan, or break into. The home reaches out to its services; the internet has no door to reach back through.
Works with what you already own
Home Assistant ships 1,500+ integrations covering thousands of smart-home devices — the brains HomeAI reasons on top of. We don't pretend we've personally certified all of them. Here's the honest breakdown of where each one stands.
The exact devices we run and tested in our reference home — in production today.
Supported through Home Assistant and expected to work — we verify each one against YOUR exact setup during onboarding. Not yet individually certified by us.
These talk only to their maker's servers, so they depend on that vendor's cloud. We support them — and we label them honestly.
Bring your devices. The beta is how we verify your exact setup — we onboard each founding home by hand and confirm every device against your house before we call it done.
Brand names are integrations supported through Home Assistant and are trademarks of their respective owners. HomeAI is vendor-neutral and not affiliated with or endorsed by any of them. Local-first coverage depends on each device's own capabilities; cloud-dependent integrations are labeled as such. Integration count per home-assistant.io.
The reference home
We don’t have a wall of testimonials — we’re in invite-only beta. We have something better: the founder’s own home, running the whole platform in production.
It caught my garage open at 11pm and texted me the envelope — not the footage. I knew what to do without ever pulling up a camera feed.
This is our first and only home so far, and we say so on purpose. As Founding Homes come online, real owners — not us — will fill this space.
Questions, answered
vault:// pointers, never written to a log. The home reaches out for the few things it needs (a weather feed, a push notification), and if you turn on an optional cloud AI model your conversation text goes to your chosen provider — with an automatic guest-facing disclosure while it’s on.Founding Homes · private beta
HomeAI is in invite-only private beta — we onboard each Founding Home by hand. Beta requests are open, and we'll reach out to set up your home. It's local-first by default, so your data stays in the house unless you turn on an optional cloud feature.