Your home lives on someone else's server
Cameras send your living room to a vendor's cloud. You can't see who looks at it, how long it is kept, or where it goes after a breach or a takeover.
nn runs your cameras, sensors and automations on boards you own, on your own network. No cloud account, no subscription, and no company that can switch your house off.
You buy the hardware, but the vendor keeps the keys. Four things go wrong again and again.
Cameras send your living room to a vendor's cloud. You can't see who looks at it, how long it is kept, or where it goes after a breach or a takeover.
When the servers shut down or the app leaves the store, hardware that still works stops working overnight. You paid for it; you can't keep it alive.
Locked bootloaders, closed firmware, no spare parts. Once updates stop, security holes stay open, and the only repair left is the bin.
A switch and a lamp in the same room, yet the decision travels to a data centre and back. When the link or the hub drops, the house stops listening.
Each one answers one of those problems. They are the rules nn is built by, not features that can be switched off later.
Video, sensor readings and automations stay in your home. The internet is optional: when it drops, cameras still record and lights still switch. Remote access is yours to add, behind your own login.
Every device runs firmware you can rebuild from public source and update from your own hub. No vendor account, no locked bootloader, no update server that can disappear.
Automations are compiled on the hub and run on the sensors themselves, over the Thread mesh. A button still switches a lamp while the hub is off or restarting.
ESP32 modules, a BeagleY-AI, an Orange Pi: boards anyone can buy. Replace a broken part yourself, and keep what you learn for your next project.
Motion is checked five times a second. Only when something moves does the object detector wake up, on the camera's own AI accelerator or on the hub's, so the chip stays cool and the recordings stay yours.
Buttons, lights and sensors talk to each other over a Thread mesh radio. You write the rule in the hub's web app; the hub compiles it and hands it to the devices, which run it themselves.
An Orange Pi 6 Plus or any Debian machine becomes the hub. It sets new devices up over Bluetooth, keeps their records, serves the web app and records camera events. Running the script again is the update.
The hub signs every firmware image and sends it over the air. A device installs only an image it can verify, and goes back to the previous one by itself if the new one fails. You can rebuild every image from the public source.
The dashed path is the only one that leaves the house, and it exists only if you add it.
Solid lines stay on your network; the dotted amber lines are the Thread radio mesh. Cameras send video to the media server; the hub keeps the control channel and its keys never leave it.
No proprietary hub and no special radios. The manual walks you through each one.
Or any Debian machine. Its AI accelerator runs detection for the cameras.
IMX708 camera module, AI on the board, can act as the mesh gateway.
A low-power camera with an ESP32-C6 for Wi-Fi 6 and Bluetooth.
Thread, Bluetooth and Wi-Fi in one module for sensors and the radio gateway.
Follow the manual on your own hardware, report what was unclear, send a fix, or bring nn to a board you love.
nn is young and made by a small team. Parts of it are still rough, and that is where your help counts most. Every contribution is read, and your name stays on it.