The hub.
An always-on place for permissions, qualified integrations, routines and evidence. The pilot does not require a custom circuit board.
Nereli brings a local hub, a mobile interface and reviewed device integrations together. Not another universal remote. A way past the setup.
An always-on place for permissions, qualified integrations, routines and evidence. The pilot does not require a custom circuit board.
A clear way to discover, approve, operate and recover. Native setup bridges are an engineering requirement, not something a browser mockup can replace.
An assistant proposes. A controlled service checks authority and runs an approved operation. Fresh evidence decides what the interface may claim.
Find the device.
Ask for the right access.
Do the useful thing.
Check what happened.
Expired authorization, an unreachable hub, and a missing completion report are different problems. The app treats them that way.
Keep room maps and routines intact. Ask you before any paused routine resumes.
See the experienceShow a timestamped last-known state. Block commands instead of queuing a surprise.
See the experienceAn accepted command is not a finished task. Unknown outcomes stay visibly unknown.
See the experienceNo. The proposed architecture uses a capable gateway with qualified device adapters. A device needs a usable, authorized interface for the requested operation—not its own language model.
No. Some device families need a manufacturer account, initial setup or a vendor-specific feature. The intended product discloses that handoff before you begin and preserves progress around it.
No. It means local execution and authority where supported. Some devices and integrations still require a vendor cloud. Compatibility must be stated by exact model and operation.
Nereli is in development. Public availability, final pricing and the supported-device catalog will be announced as the pilot is qualified. Visit the pilot page for updates.