Search for a smart home hub and you will be shown four different categories of product under the same word. A Zigbee bridge is called a hub. An Echo is called a hub. Home Assistant is called a hub. A $10 dongle is called a hub.
They do genuinely different jobs, and the confusion has a cost: people buy the wrong one, conclude smart homes are a mess, and are not entirely wrong.
This is an attempt to make the categories clear, including where a local AI hub fits and where you would be better off with something else.
The four things people call a hub
A radio bridge translates one protocol. A Zigbee or Z-Wave stick lets your computer talk to devices that do not speak Wi-Fi. It has no opinions and no intelligence. It is a translator.
A cloud hub is an Echo, a Nest, or a SmartThings box. It connects to your devices and sends the interesting parts to a vendor's servers, where the decisions are made. It is inexpensive, capable, and dependent on both an internet connection and a company's continued interest in supporting it.
A local controller is Home Assistant, Homey, or Hubitat. Devices connect to a box in your house, and automations run there. Nothing needs to leave the building for a light to turn on. What these do is execute rules — rules that you write.
A local AI hub is a local controller that also tries to work out what the rules should be. It observes what actually happens in the house and proposes automations rather than waiting for you to specify them.
The first three exist and are mature. The fourth is the newest and the least settled, and it is where Nexop sits.
What "local" is actually protecting
Local processing gets discussed as a privacy feature, which undersells it. There are three separate benefits and they matter to different people.
Privacy is the obvious one. Occupancy, sleep patterns, and comings and goings are unusually revealing data. A local system does not need to transmit them to be useful.
Reliability is the one people feel most. If the automations run in your house, your lights work when your broadband does not, and when the vendor has an outage. Cloud smart homes fail in a specific and infuriating way: everything is powered, connected, and unresponsive.
Longevity is the one people notice too late. A cloud device works until the company decides otherwise. The graveyard of discontinued smart home products is large and growing, and none of those devices stopped working because the hardware failed.
Local-first does not mean offline-only. Remote access and updates are perfectly reasonable uses of the internet. The distinction is whether your household context is the thing being shipped away, and whether the house stops working when the connection does. We wrote about that difference in more detail in what local-first AI actually means.
Curious whether Nexop fits your home?
Book a live demo — one of the founders runs it, not a salesperson — or join the waitlist and hear from us the day it ships.
Where the AI part comes in
Here is the honest situation with most local controllers today: they are powerful, and they put the work on you.
You decide that the hallway light should come on when motion is detected after sunset, but not if the living room is already occupied, and not after midnight unless someone has just come through the front door. Then you build that. Then you discover the edge cases, and you maintain it.
People who enjoy this are well served already, and Home Assistant in particular is superb for them. The problem is everyone else, who buys the hardware, builds three automations, and stops.
A local AI hub is a bet that the bottleneck was never capability. Your home already produces the signal needed to work out that you dim the lights at around ten on weeknights. Something should be able to notice that and offer it to you, rather than waiting for you to specify it in advance.
The important word is offer. A system that changes your home based on inference, without asking, is not helpful — it is unpredictable, and unpredictable is worse than manual. The useful version observes, proposes, and lets you approve, edit, or ignore.
How to tell which one you need
Buy a radio bridge if you already have a system you like and just need it to speak to a device it currently cannot.
Buy a cloud hub if you want the cheapest capable option, you mostly want voice control, and processing in someone else's data centre genuinely does not bother you. This is a legitimate position and the value is real.
Buy a local controller if you want your home to keep working independently of the internet, and you are willing to build and maintain the automations. If you enjoy that, you will hit its limits long after you hit ours — Home Assistant and Homey Pro are both excellent, and Homey in particular supports more radio protocols today than we will at launch.
Consider a local AI hub if you want the independence of a local controller but you do not want a permanent configuration project. That is the specific gap Nexop is built for.
What to actually check before buying
Whatever category you land on, four questions separate the marketing from the product:
Does it work when the internet is down? Not "does it have local control as a feature", but does the whole thing keep running. Ask what specifically stops.
What does it cost to keep? One-time purchase, subscription, or a free tier that will eventually need to make money. All three are viable business models; you just want to know which one you are entering.
Which protocols are native? Zigbee, Z-Wave, Matter, Thread, KNX, and plain Wi-Fi are not interchangeable. Check against the devices you already own, and check whether a protocol is built in or needs an add-on dongle.
Who owns the data, in writing? Not the marketing page. The privacy policy.
Where Nexop stands
Nexop is a local AI hub: it plugs into your network, natively supports Zigbee, KNX, Matter, and Wi-Fi, learns your household's routines locally, and proposes automations you approve. One-time purchase, no subscription.
It is also pre-launch, which is the most important thing on this page. The products it competes with are shipping today and ours is not yet. If you need a hub this month, buy one of the ones we linked above — genuinely. If the proactive part is what you have been waiting for, join the launch list or book a demo and watch it run on a real home before you decide anything.