Every smart home quietly stops working.
Nobody can tell you why.

That is the actual unmet need in home automation. Not more integrations, not cheaper switches — an answer to "why did the light not come on?" that is not a shrug.

The HomeHub manifesto · Last updated: 25 July 2026

We cannot out-integrate Home Assistant; three thousand integrations is a decade of community effort. We cannot out-cheap Tuya; their moat is bill-of-materials cost. Competing on either is choosing to lose slowly.

So we compete on the thing neither of them sells:

Home Assistant sells freedom. Keus sells luxury. We sell legibility and reliability — a home that will still work in ten years, and that can tell your electrician what it is doing.

Seven commitments. Each one is a thing we have built, not a thing we aspire to.

1Local-first. Your home works when the internet does not.

Every decision is made in your house, by a hub in your house. Lights, scenes, schedules, rules, sensors, locks — all of it runs with the WAN unplugged.

Remote access exists, and it is built the right way round: the hub dials out to a relay you host. No inbound port, no port forward, nothing of yours listening on the internet. Your data leaves your home only when you push it.

2The hub orchestrates. Edges control.

Anything needing hard real-time — pump pressure, motor ramps, safety interlocks — runs on the edge device and keeps running when the hub is gone. This is not a limitation we are apologising for; it is the safety story. A home whose interlocks depend on a server being alive has a single point of failure in the wrong place.

3The hub explains every decision.

Every automation evaluation is recorded with why, in a sentence a person can read:

And for any device, at any time: why is this like this? — what last changed it, what caused that, which automations could have acted, what each of them decided, and whether the state you are looking at is even live.

No competitor demos this, because everyone demos the light turning on. We demo the light not turning on, and the home explaining itself.

4Drafts never act. Approval is a human act.

The assistant proposes. A person disposes.

An AI credential is the least privileged identity in your home — below a guest. Irreversible actions (unlocking a door, starting a pump) are enumerated in code, not described in a prompt. When the assistant wants one, it becomes a proposal you approve in the app — and it cannot approve its own request.

"The AI acted on my house" is coming for this industry. It will not come from here.

5Nothing breaks silently.

A device that stops reporting is noticed, and the hub tries to fix it itself — re-probing, re-subscribing, restarting the integration — before it wakes you. If it recovers, you get a line saying it healed itself. If it does not, you get one notification that says what was already tried.

A misbehaving integration cannot take down your home: drivers run in their own process, so a crash restarts an integration, not a house.

And our reliability claims are measured, not asserted: 99.9% of scheduled firings within 2 seconds, visible in diagnostics on your own hub, counting our own restarts against us.

6Your data is yours, and your home is not for sale.

No telemetry. No analytics. No account required to use your own house. History lives on your disk and exports in one click. Snapshots are versioned and migrated in place, because a hub update must never eat a home.

We will never monetise access to your house. If we ever want money from you, we will ask you for it.

7An auditable core, and we will tell you what is in it.

Zero unaudited dependencies. Three protocol and crypto libraries are allowlisted with a written justification, pinned by hash, installed without executing anything, and optional at runtime — and the hub tells you which implementation it actually loaded.

We do not hand-roll crypto we have no business hand-rolling.

What this costs us, stated plainly

Being legible is slower than being magical. Asking for confirmation is more friction than acting. Refusing to expose a lock over an unauthenticated protocol means one fewer tick on a feature matrix. Certifying hardware means saying "we have not tested that" out loud.

We accept all of it. A home automation system is infrastructure in someone's house, often controlling their front door. The right posture for infrastructure is boring, predictable, and honest about its limits.

How to hold us to it

Every commitment above is checkable on your own hub:

/api/v1/diagnostics        the error budget and what is actually loaded
/api/v1/explain?deviceId=  why is this device like this
/api/v1/traces             why did each automation run, or not
/api/v1/certification      is this hardware actually tested
/api/v1/bridges            exactly what is exposed to your network
/api/v1/backup             your home, portable, right now

If any of them ever tells you something that is not true, that is the most serious kind of bug we have, and we want to hear about it: hi@techmanjeera.com