DownloadsNode
Install Sophon Node
01With the .NET runtime
One command.
dotnet tool install -g sophon-nodeRequires the .NET 10 runtime on the machine. Upgrade with dotnet tool update -g sophon-node.
02Without it
A single file, runtime included.
Windows · x64
v2.2.2 · ~35 MB
Single file, runtime included. Extract and run
sophon-node pair.Verify download (SHA-256)
sophon-node-win-x64-self-contained.tar.gz
a64b81e5c831f704122c10471710c036d25fdf51e0c7b1177b1adb162f5e6b52macOS · Apple Silicon
v2.2.2 · ~33 MB
Single file, runtime included. Extract and run
sophon-node pair.Verify download (SHA-256)
sophon-node-osx-arm64-self-contained.tar.gz
8afac480e51177c188b5cea262219d7c84f2a2b2a2d827b0a2879a3c144ab4a7Linux · x64
v2.2.2 · ~35 MB
Single file, runtime included. Extract and run
sophon-node pair.Verify download (SHA-256)
sophon-node-linux-x64-self-contained.tar.gz
3efcb1ef731177602e4358cf1421558415bd12231351386fd9b37290357cae3c
Node builds are not code-signed yet, so Windows and macOS will flag them as coming from an unidentified developer. Signing is on the roadmap; until then the SHA-256 above is the check that the file is the one we built.
03After installing
Installing is only half of it.
Your approval
A Node does nothing until you pair it with a Gateway and approve that pairing in the Dashboard. Approving a device grants it a starting set of scopes. Shell execution is not one of them. On-device confirmations are separate from Gateway approvals; the owner can manage them from the Dashboard in v2.2. A local lock prevents Sophon from disabling confirmations or widening folder access.
The node CLI has 8 top-level commands
- sophon-node pair
- sophon-node start
- sophon-node status
- sophon-node unpair
- sophon-node lock
- sophon-node unlock
- sophon-node settings
- sophon-node version