Binary Deployment

Binary deployment runs Komari directly without Docker. It is useful when you want a simple executable plus a system service.

TLDR

Download the matching file from the GitHub Releases page, then start Komari:

./komari server -l 0.0.0.0:25774

On Windows:

.\komari.exe server -l 0.0.0.0:25774

Download Komari

1. Open the GitHub Releases page.
2. Download the asset for your operating system and CPU architecture.
3. Rename it to komari or komari.exe.
4. Place it in a dedicated directory, such as ~/komari on Linux or C:\komari on Windows.

Make It Executable

Linux and macOS only:

cd ~/komari
chmod +x komari

Start the Server

./komari server -l 0.0.0.0:25774

Komari creates a data directory in the working directory. Do not delete it unless you intentionally want to remove local data.

Find the Initial Login

On first start, Komari prints the default admin account in the terminal:

Default admin account created. Username: admin , Password: 2ioEnIPwn17a

Open http://localhost:25774 or http://<your-server-ip>:25774 and sign in.

Run as a Linux Service

Create /etc/systemd/system/komari.service:

[Unit]
Description=Komari Monitoring Service
After=network.target

[Service]
ExecStart=/home/user/komari/komari server -l 0.0.0.0:25774
WorkingDirectory=/home/user/komari
Restart=always
User=root

[Install]
WantedBy=multi-user.target

Replace /home/user/komari with the real installation path.

Enable and start it:

sudo systemctl daemon-reload
sudo systemctl enable komari
sudo systemctl start komari
sudo systemctl status komari

Useful service commands:

sudo systemctl stop komari
sudo systemctl restart komari
journalctl -u komari -f

Troubleshooting

• If the binary will not run, confirm that you downloaded the correct architecture and set executable permissions.
• If the dashboard is unreachable, check the listen address, firewall, and service status.
• If a service fails to start, inspect journalctl -u komari -f and verify the paths in the service file.