Install the desktop app

Downloads for macOS, Windows and Linux, what to expect on first launch, and where your data is stored.

Get the installer from the download page. It detects your platform and offers the right build first; every build is listed underneath with its size and SHA256 checksum.

Platform	Build
macOS, Apple Silicon	`.dmg` (arm64)
macOS, Intel	`.dmg` (x64)
Windows	`.exe` installer (x64)
Linux	`.AppImage` or `.deb`

Pick the right macOS build

Apple Silicon is anything M1 or later. If you are unsure, open the Apple menu → About This Mac and look at Chip. The Intel build will run on Apple Silicon under Rosetta, but slower and with more memory.

Verifying a download

Each listed build shows a SHA256. To check it before installing:

shasum -a 256 ~/Downloads/Triagic-*.dmg

Get-FileHash "$env:USERPROFILE\Downloads\Triagic-Setup.exe" -Algorithm SHA256

The output should match the checksum on the download page exactly.

macOS

Open the .dmg and drag Triagic into Applications.
Launch it from Applications.

If macOS refuses to open the app because it "cannot verify the developer", the build you downloaded is unsigned. Right-click the app and choose Open, then confirm — or clear the quarantine flag:

xattr -dr com.apple.quarantine /Applications/Triagic.app

Only do this for a build you downloaded from the official download page and whose checksum you verified.

Windows

Run the installer. If SmartScreen warns about an unrecognized publisher, choose More info → Run anyway — again, only for a verified download.

Linux

AppImage — make it executable and run it:

chmod +x Triagic-*.AppImage && ./Triagic-*.AppImage

Debian / Ubuntu:

sudo apt install ./triagic_*_amd64.deb

First launch

The app starts a local server bound to loopback and opens the UI against it. Nothing listens on a public interface.

On first run it creates its data directory and generates a local encryption key. That key is what protects every credential stored on this machine.

Platform	Data directory
macOS	`~/Library/Application Support/Triagic`
Windows	`%APPDATA%\Triagic`
Linux	`~/.config/Triagic`

Back up the encryption key, or accept re-entering credentials

Losing the data directory means losing the key, and stored secrets can no longer be decrypted — affected integrations will report cannot decrypt stored secrets and have to be re-entered. If your organization uses shared integrations, this matters less: those re-sync from the portal on the next pull.

Updates

The app checks for updates on its own and installs them on restart. There is nothing to do.