Most hubs wait for you to write the rules. Nexop watches how your home actually runs for a week, then proposes automations you approve, edit or ignore. Everything runs on the box. Simple commands land in ~0.3s without calling the model at all. Describe an automation in plain English — "every weekday at 7pm", "when there's no motion for 5 minutes" — and it's written and live in seconds. Native Zigbee, KNX, Matter and WiFi. One-time purchase. No subscription, no cloud.
No reviews yetBe the first to leave a review for Nexop
Maker
📌
Hey Product Hunt 👋
I'm Abdulhusein, one of two founders. Husain and I have spent this year on a
single annoyance: every smart home hub is a rules engine waiting for you to
write the rules. So you write four, they break the first time your schedule
changes, and an expensive box becomes a light switch with extra steps.
We wanted the opposite — something that watches how you actually live and
comes to you. Nexop observes for 7 days, then starts proposing automations.
You approve, edit or ignore them. Nothing happens in week one, on purpose.
That meant the AI had to live in the house rather than a datacentre, so it
runs on the appliance itself — an NVIDIA Jetson with a small model on it.
Two things fell out of that we didn't plan for. Most commands never reach
the model at all: a local matcher handles "turn off the kitchen lights" in
about 0.3 seconds. And because it's your hardware, there's nothing for us
to meter. One-time purchase, no subscription.
The hardest part was KNX — what most high-end installed homes actually run
on, that no consumer hub supports. The device map lives in a project file on
the integrator's laptop, so we import that file and build your home from it.
Watching it drive a real KNX bus in June was the best day of the project.
Where we are: the software runs on real hardware and we demo it daily. No
mobile app yet, and no drag-and-drop automation editor — you talk to it
instead. We're pre-launch, so this is demos and the waitlist, not orders.
Genuine question for this crowd: if a hub proposed an automation to you
tomorrow, what would it have to show you before you'd hit approve?