Frequently asked questions.

Nexop is a local-first AI hub for the smart home. It plugs into your network, finds the devices you already own, learns how your household really runs, and then proposes automations you can approve, edit or ignore.

The intelligence lives on the device in your home rather than in a remote cloud service, and it's a one-time purchase with no subscription.

Alexa and Google Home are voice assistants: you ask, they do. They're reactive, they depend on the cloud, and the useful parts of your household context sit on somebody else's servers.

Nexop is a home manager rather than an assistant. It watches how you live and suggests automations you never had to think of, and it runs locally so your routines stay in the house. You can still talk to it in plain English when you want to.

It means the core intelligence runs on hardware you own instead of depending on a remote server. Routine learning, device state, and automations are processed in your home.

Local-first isn't the same as offline-only. The internet is still useful for things like updates and remote access. The difference is that your household context isn't the thing being shipped away.

Most smart homes wait for instructions. Nexop spends its first week quietly observing: when you wake, when you cool the house, who comes and goes. It takes no actions during that time.

After that it starts proposing automations based on what it saw. You approve the ones that make sense, edit the ones that are close, and ignore the rest. Nothing runs just because Nexop decided it should.

No. Nexop isn't a Home Assistant add-on and doesn't sit on top of one. It natively supports the integrations Home Assistant supports, so you don't need to install, configure or maintain anything else first.

If you already run Home Assistant and enjoy it, nothing stops you. Nexop just doesn't require it.

Zigbee, KNX, Matter, Bluetooth and WiFi are supported natively, which covers most of what's already in modern homes. On Zigbee alone that is over 3,400 supported devices.

The aim is to work with the devices you own rather than asking you to replace them. Nexop sits in the middle of your existing setup instead of becoming another ecosystem to buy into.

Auto-discovery handles the common case, and there's a manual fallback for the rest. A device that doesn't announce itself cleanly can be added by hand rather than being unsupported.

The parts that matter keep working. Automations run locally, so a dropped connection doesn't stop your lights, climate or routines from behaving normally.

Features that are about the internet by nature, such as reaching the house from outside it, need a connection.

Nexop is designed so that household data stays on the local device by default. That includes routine learning, device state, occupancy signals, and automation history.

A home produces unusually revealing data: when you sleep, when you're out, which rooms are occupied. We treat that as yours, not as a dataset.

No. Nexop is a one-time purchase, and there are no monthly fees or cloud charges to keep it running.

Subscriptions make sense when a product depends on somebody else's servers to keep running. Nexop doesn't, so charging rent for it would be hard to justify.

Pricing hasn't been announced yet. What's settled is the shape of it: a one-time purchase, no subscriptions, no cloud fees.

We'd rather publish a number we intend to keep than a placeholder we quietly change later. Waitlist members hear the final pricing first, on launch day.

There's no fixed launch date, and that's deliberate rather than evasive. Nexop is pre-launch and we're building it iteratively, so announcing a date we aren't sure of would help nobody.

The launch list is the reliable way to hear when it ships. If you'd rather see where the product is today than wait, you can book a demo and watch it run on a real home.

Yes. A demo is 30 minutes, run by one of the founders, on a real home rather than a slide deck. You'll see what works today, and we'll be straightforward about what's still being built.