Server Binary

The native server package includes stib-server, the embedded web interface, and the stib command-line client used by agents. Published server builds include the system-tray feature; it is disabled automatically when no graphical display is available.

Packages

Download from stib.ai/download.

Platform	Architectures	Server artifacts
macOS	ARM64	DMG, PKG
Windows	x64, x86, ARM64	MSI
Linux	x64, ARM64	DEB, tar.gz

Install and run

macOS

Install the PKG or copy stib-server.app from the DMG, then launch it from Applications. The release is signed and notarized.

Windows

Run the MSI for the machine architecture, then start Stib Server from the Start menu or terminal.

Linux

sudo apt install ./stib-server-*.deb
stib-server

For another distribution, unpack the tar.gz, install the two binaries, and use the included systemd unit as a template.

Listening address and port

The release server listens on all interfaces. It first tries port 50505, then 50506 through 50514, and finally an OS-assigned port if the range is unavailable. The actual port is written to port.txt in the server data directory and shown by the tray UI when available.

Open http://localhost:<port> for the embedded web client or enter that origin in the desktop app.

Data directory

Native installations use the operating-system application data directory:

Platform	Directory
macOS	~/Library/Application Support/stib-server/
Windows	%LOCALAPPDATA%\stib-server\
Linux	~/.local/share/stib-server/

The directory contains data/stib.db, attachments, backups, logs, update staging files, the server UUID, and port.txt. Migrations run automatically when the server starts.

Verify

curl http://localhost:50505/api/health

If the port changed, substitute the actual value. A healthy response is wrapped in Stib's standard data object.

Updates

Native servers check the signed update manifest for their stable or beta channel. A supported package update uses PKG on macOS, MSI on Windows, and DEB on Linux. Tarball installations should be updated manually. Docker installations are never self-replaced; pull a new image instead.

An update that changes the database schema backs the database up before migrating it, and puts that backup back if a migration fails — see Backups before migrations. That copy stays on this machine: to keep one elsewhere, create a backup from Settings → Server → Backup before updating, and keep any environment-managed encryption key available.

Next: Configuration.