Choose and verify an installation

1. Choose the operating mode

Use the desktop command center for the native window, tray, notifications, autostart, and signed updater. Use the headless CLI for SSH hosts, CI, WSL2, or a browser-only workflow.

The download page shows only assets returned by the GitHub Releases API. If a verified stable package is unavailable, it says so instead of guessing a filename.

2. Verify before installation

From the same release, verify the asset checksum, platform identity, GitHub attestation, and SBOM as applicable. Follow the verification guide for exact commands.

3. Confirm local capabilities

switchyard doctor

Expected success is a versioned report with local IPC, database/schema, Git, and the adapters available on this machine. Docker may be unavailable when the first project uses only native processes.

4. Open the product

switchyard ui

The command prints a short-lived authenticated loopback URL. Do not paste that URL into an issue or support bundle. The browser should show the empty project state and remain usable when Docker is disconnected.

Next: add your first project.