One box at home. Every machine you own inherits it.

English · 中文

A neutrino passes through walls without touching them.

The wall is still there. It just stops being yours.

Install · Documentation · What it does · Panel · Why

What it does

In one line: the hub manages your machines and publishes the services they provide; a client on your LAN, or one that reaches the hub from outside through the overlay, gets the same services.

Each part has its place. The hub runs on one always-on Linux box and handles the network, the overlay, the proxy and the AI gateway. The agent runs on every Linux machine you manage and provides that machine's shares, git server, containers, storage and desktop. The client runs on every computer you sit at and turns those services into buttons in a window.

Supported platforms

Install

sudo apt install ./neutrino-hub_0.2.0_amd64.deb
sudo nhub setup

nhub setup opens a six-screen wizard in your browser. When it finishes, the panel is at http://<hub>:8080, where <hub> is the box's address.

sudo dnf install ./neutrino-hub-0.2.0-1.x86_64.rpm
sudo nhub setup

On RHEL, AlmaLinux and Rocky, run sudo dnf install -y epel-release first: fail2ban, arp-scan and vnstat come from EPEL. The wizard then runs as it does on Debian, and the panel is at http://<hub>:8080.

sudo pacman -U neutrino-hub-0.2.0-1-x86_64.pkg.tar.zst
sudo nhub setup

Setup runs the same six-screen wizard, and the panel is at http://<hub>:8080 afterwards.

sudo apt install ./neutrino-agent_0.2.0_amd64.deb      # Debian family
sudo dnf install ./neutrino-agent-0.2.0-1.x86_64.rpm   # Fedora family
sudo nagent connect '<link>'

<link> is what Add by link on the Devices page shows; it is valid for five minutes, and the machine then appears under Managed devices.

sudo apt install ./neutrino-client_0.2.0_amd64.deb      # Debian family
sudo dnf install ./neutrino-client-0.2.0-1.x86_64.rpm   # Fedora family
nclient gui

Run the client from your own account, then paste the link from the Clients page into the window.

msiexec /i neutrino-client-0.2.0-windows-amd64.msi                    # Windows
sudo installer -pkg neutrino-client-0.2.0-macos-arm64.pkg -target /  # macOS

Opening the .msi from Explorer, or the .pkg from its context menu with Open, runs the same installer. The Windows installer offers to put nclient on PATH. The client then sits in the taskbar corner on Windows or in the menu bar on macOS.

Every file is on the releases page, and the site's install pages have the screenshots: the hub, the agent and the client.

Documentation

Quick start · Overview · Troubleshooting

The services

The panel

Dashboard: throughput, active exits and DNS queries.	Proxy: exit nodes and split routing.
AI: providers, accounts and keys.	Devices: managed and unmanaged machines.
Services: the four published groups.	Samba: shares, users and sessions on one machine.

What runs where

The three packages share one version number, and the panel marks an agent or a client on another version for upgrade. The hub's own machine runs an agent too, as one device among the others. Every module runs under an agent on the machine that has the disk or the GPU, so the hub box stays small.

Security

• The hub and the agent run as root; the client runs as the person, and its one privileged step is a polkit helper that mounts a share.
• The panel is plain HTTP, for the LAN and the overlay: the password is not protected from someone reading the wire, so keep the panel on a network you own. It is protected from guessing: five free attempts, then each failure locks login for 30 s, 60 s, 5 min, an hour, a day; and fail2ban bans an address that hammers SSH on the same ladder.
• Everything between the hub and its agents and clients is TLS. An enrollment link is valid for five minutes and is consumed once, and the channel pins the hub's certificate by the fingerprint inside that link, so a machine that joined speaks only to the hub it joined.
• The vault is sealed under the passphrase set during setup.

Why I built it

Reaching the tools was the first problem.	I go travelling. The workstation does not.
No machine of mine is difficult. All of them together are.	Data grows quietly.
Everything worked. Each thing lived somewhere else.	I was tired of copying the same keys around.

pip install -e "hub[dev]" && pip install -e agent && pip install -e client
black --check hub agent client
cd hub && pytest -q
cd hub/frontend && npm run build
nhub apply --dry-run

Python 3.12 or newer, Node 24 or newer, black and pytest; hub/, agent/ and client/ are the three packages, config/ the source of truth at runtime, docs/ the site and packaging/ the VM rig. The contributor standard is AGENTS.md.

Acknowledgements

Neutrino configures and includes work by others:

• Xray-core, the proxy core behind the Proxy page
• CLIProxyAPI, the AI gateway
• cpa-usage-keeper, the usage metering beside it
• NetBird, one of the two overlay engines
• EasyTier, the other overlay engine
• cc-switch, which points the AI tools at the gateway
• RustDesk, the remote desktop host and viewer
• Gitea, the git server a machine hosts
• Samba, the SMB server a machine hosts
• Podman, the container runtime a machine hosts
• OpenZFS, the pools and datasets a machine hosts
• dnsmasq, DHCP and DNS on the served networks
• hostapd, the access point on a wireless LAN
• v2fly geodata, the direct lists for split routing

Claude Code and ChatGPT assisted with implementation, debugging, design and documentation; the author reviews every release.

License

MIT.

Let creation be fun again.

Spend less time maintaining the environment.

Spend more of it on whatever made you build one in the first place.