Under the hood
Your home shouldn't depend on hope. Huze is built the way serious systems are built, with layers of resilience, an escape hatch under every failure, and proof instead of promises.
Resilience, in layers
Every layer assumes the one above it can fail. That's not pessimism; it's how you build something a family can depend on.
Every update installs alongside the running system and only takes over after proving itself healthy. A bad update rolls itself back automatically, and beneath even that sits a rescue layer that can always bring the box home. We rehearse these failures deliberately; the recovery is drill-proven, not theoretical.
Storage, temperature, connectivity, the health of every capability it offers. The box continuously checks that everything it claims to do, it can still actually do, and flags trouble before you'd notice it.
The box keeps two weeks of its own configuration and data history on board. A mistake in your setup is an undo, not a rebuild.
Once your home is configured, that configuration is an asset. The offsite plan keeps an encrypted copy away from the house. Fire, flood or theft: your smart home comes back with the replacement box.
Add the UPS option and the box glides through short outages, and shuts down gracefully, never messily, through long ones. Your configuration and history are protected against even a hard cut.
The home itself never needs the internet to run; that's the architecture, not a feature. Add the mobile-data option and the box can still reach you during a broadband outage: alerts, care notifications and health signals keep flowing.
Your data
Privacy policies change. Architecture doesn't. Huze is private because of where things run, not because of what a document promises.
Automation, history, presence, care: all of it runs and is stored in your house. No instruction crosses the internet to be acted on, so there's no round-trip delay, no outage dependency, and no cloud account holding your home's behaviour. That was the founding architecture decision, and everything else on this page follows from it.
Anything that does leave the house, offsite backups or health reports, is encrypted before it leaves, with keys that stay with your box. We store it; we can't read it. Nobody can.
The box actively polices what's allowed out of your network, out of the box. Data protection isn't a setting you have to find; it's the factory default.
Support
Remote support is off by default: nothing listening, nothing connected. A session starts only when you press the button, lasts only as long as you allowed, ends by itself, and is logged at both ends. We can never let ourselves in.
With the health-reporting plan, your box sends us its (encrypted) vital signs. Failing storage, a struggling sensor network, a device going flaky: we see it early and often fix it before it touches your home.
Priority help from people who can see your box's health picture (never your home's private data), so support conversations start at "we can see what's wrong", not "have you tried turning it off and on".
Speaks fluent home
One box, many radios and protocols, including the legacy ones the industry has left behind.
Rich, instant notifications to your phone are included from day one: events, care alerts, energy nudges, health warnings.
Add text messages, WhatsApp and spoken phone calls for the moments that must never be missed, and for the family members who will never install another app.
Notification channels aren't just outputs. The care system uses them in sequence, escalating from a quiet message to a phone that actually rings.
Say "Alexa, bedtime" and Huze runs the whole choreography: lights ramp down, warmth eases back, sockets you never trust overnight switch off. You choose exactly which devices Alexa is allowed to see, and the routine itself runs on the box. The voice is the only part that touches a cloud.
Launching soon
We like those. Get in touch and we'll answer what we can, and be honest about what we're keeping under the lid.