Control everything. Share nothing.

Nemu, a cozy sleepy chicken mascot waving hello

A quieter kind of smart home. Open-source control that keeps your devices, your data, and your everyday life on your network.

Nemu, a cozy sleepy chicken mascot waving hello

Smart home. Private Life.

Nemu looking calm while your home stays on the controller

Privacy by design

Your controller keeps devices, state, automations, and history. The cloud can coordinate who reaches it, but it never holds a readable copy of your home.

Nemu spinning happily on your own network

Local-first, cloud when needed

On your network, control stays local and keeps working if the internet drops. If that path is down, a paired app falls back to an end-to-end encrypted relay, then returns to the LAN as soon as it can.

Nemu taking notes on the open-source code

Open source, inspectable

Read the code, fork it, and run the controller yourself. Nemu is Apache-2.0, so you can see what runs inside your home.

How it works

Your home. Your rules. Your network.

A controller on hardware you own. Devices stay on your LAN, and the cloud only coordinates who can reach them.

01Run the controller at home

Install Nemu on a home server or a Raspberry Pi. Each Home has one Controller, and you own the hardware.

02Keep devices on your network

Matter and Zigbee connect locally. Lights, locks, and sensors answer on your LAN.

03Connect from your apps

A phone or browser pairs on the network. Away from home, it falls back to an end-to-end encrypted relay.

Everyday control

Everything you need. Nothing watching.

LAN-speed control

On your network, apps talk to the Controller directly. A switch flips without a round trip through a vendor cloud.

Real-time updates

While you are on the LAN, device state arrives as it changes. Connected apps stay in sync with the Home.

Matter and Zigbee

Lights, locks, sensors, and plugs join the Controller. Capabilities describe what you can read and change.

Self-hosted controller

One Controller per Home, on hardware you run. It keeps devices, rooms, state, automations, and history.

Privacy by default

The cloud can coordinate who reaches the Controller. It never holds a readable copy of your home.

Relay when you leave

Away from the LAN, a paired app falls back to an end-to-end encrypted relay, then returns as soon as it can.

A home. Not a data source.

Typical cloud hub

Someone else's server.
Nemu unimpressed by a house that lives on someone else's server

Device data routed through vendor servers

Control tied to a company's terms and availability

A home profile that lives outside your home

With Nemu

Your network. Your controller.
Nemu waving, happy the controller stays at home

Control runs on hardware you own

LAN first, with an encrypted relay when you leave

Open code you can inspect, fork, and self-host

Open by design

Trust what runs inside your home.

Nemu is Apache-2.0. Read the code, contribute, or run the Controller yourself.

Zed-Softworks-Official / nemu

A local-first controller for a home that stays yours.
License
Apache-2.0
Built with
Rust + TypeScript
Made by
Zed Softworks
Nemu sparkling with excitement

Get early access.

Nemu is in private alpha. Join the waitlist and be first in line when a spot opens.