Native Installation
Run Sophon natively, without Docker, using the installer for Windows, macOS or Linux.
Use the installer
A native install is the installer for your platform. It bundles the .NET runtime, runs the Gateway in the background as your own user (a scheduled task on Windows, a launchd agent on macOS, a systemd user service on Linux), and serves the Dashboard at http://localhost:8470:
- Windows:
.exeor.msi, Windows 10/11 x64 - macOS:
.pkg, macOS 14+ on Apple Silicon - Linux:
.deb, Debian and Ubuntu, x64 and arm64
Without Docker, Sophon falls back to the process-based sandbox (ProcessSandboxOrchestrator) for code execution. Install Docker as well if you want the container sandbox. All other features work the same.
The .NET tool is the CLI only
dotnet tool install -g sophon-cli installs the command-line client, not a Gateway. sophon start then starts a Gateway installed by the macOS or Linux installer (port 8470 by default, or --port), or one inside a Sophon source checkout (port 8080, through dotnet run). On Windows the .NET tool doesn't find the installed Gateway; use the bundled Sophon.CLI.exe (see the Windows guide). Elsewhere it reports that it could not find the Gateway. See Installation.
Running the Gateway binary yourself
To manage the process yourself, first stop what the installer set up (schtasks /End /TN "Sophon\SophonGateway" on Windows, sophon service uninstall on macOS, systemctl --user disable --now sophon-gateway on Linux), then start the installed binary with the address it should listen on:
| Platform | Binary |
|---|---|
| Windows | C:\Program Files\Sophon\gateway\Sophon.Gateway.exe |
| macOS | /Library/Sophon/gateway/Sophon.Gateway |
| Linux | /opt/sophon/gateway/Sophon.Gateway |
/opt/sophon/gateway/Sophon.Gateway --urls http://localhost:8470Pass --urls every time. Without it the Gateway doesn't use 8470.
Configuration
User configuration is stored at ~/.sophon/config/appsettings.user.json. See the Configuration Reference for the full data directory layout and all available settings.