Download Partner

Download Partner on the computer you want to reach. It runs on Windows, Linux and macOS. On macOS you can also install just the command-line/server daemon with Homebrew, for machines with nobody at the screen.

Loading the current release…

Install from your package manager (Linux)

On Linux the tidiest option is not a download at all. Add the Partner repository once and your system keeps Partner up to date along with everything else, verifying every package's signature as it goes:

# Debian / Ubuntu
sudo install -d -m 0755 /usr/share/keyrings
curl -fsSL https://partner.gurupras.me/download/repo/apt/current/partner-archive-keyring.gpg \
  | sudo tee /usr/share/keyrings/partner-archive-keyring.gpg >/dev/null
curl -fsSL https://partner.gurupras.me/download/repo/apt/current/setup/partner.list \
  | sudo tee /etc/apt/sources.list.d/partner.list >/dev/null
sudo apt update && sudo apt install partner

# Fedora / RHEL / Rocky / Alma
curl -fsSL https://partner.gurupras.me/download/repo/rpm/current/setup/partner.repo \
  | sudo tee /etc/yum.repos.d/partner.repo >/dev/null
sudo rpm --import https://partner.gurupras.me/download/repo/rpm/current/RPM-GPG-KEY-partner
sudo dnf install partner

# Arch / Manjaro / EndeavourOS
curl -fsSL https://partner.gurupras.me/download/repo/arch/current/partner-repo-key.asc -o /tmp/partner.asc
sudo pacman-key --add /tmp/partner.asc
sudo pacman-key --lsign-key "$(curl -fsSL https://partner.gurupras.me/download/repo/arch/current/setup/FINGERPRINT)"
curl -fsSL https://partner.gurupras.me/download/repo/arch/current/setup/pacman.conf.fragment \
  | sudo tee -a /etc/pacman.conf >/dev/null
sudo pacman -Sy partner

Then upgrades are whatever you already run — apt upgrade, dnf upgrade, pacman -Syu. Setup, holding a version, downgrading and uninstalling are all covered in the package repository guide.

Pick either the repository or a downloaded package for a given machine, not both — two things trying to own the same installation will undo each other's work.

Install on macOS

Download Partner-<version>-darwin-<arch>.pkg above and open it. The package installs the Partner app into your Applications folder, and the daemon alongside it.

The daemon is installed but not started. Until you turn on unattended access from inside the app, your Mac can be reached only while the app is running — turning it on is a separate, deliberate step that asks for your password once. That is the same behaviour as every other platform. See Install on macOS.

Just the daemon, for a server

On a Mac with nobody at the screen you can install only the headless daemon:

brew tap gurupras/partner
brew trust gurupras/partner
brew install partner

The middle line is required: Homebrew will not load a formula from a third-party tap until you have trusted that tap, and brew install fails without it.

This is the command-line/server daemon only — Apple-notarized, Developer ID-signed, and kept up to date by Homebrew (brew upgrade partner). It is not the graphical Partner app, and there is no Partner Cask: if you want the app, use the package above.

Install, or just run it?

Both give you the same app. The difference is what they leave behind:

	Install	Run without installing
Needs admin rights	yes	no
Starts when you sign in	yes	no
Reachable when nobody is signed in	yes, once you turn on unattended access	no
Leaves anything behind	yes, until you uninstall	nothing to uninstall

Choose Install (the Windows installer, or a Linux Deb, RPM or Arch package) for a machine you want to reach at any time, which is what Partner is for. Choose Portable or the AppImage to try it, or on a machine you cannot or would rather not install software on.

Then what?

Per-OS steps, including how to turn on unattended access:

• Install on Windows
• Install on Linux
• Install on macOS

Once Partner is running, getting started walks through your first connection.

Verifying a download

Every release ships a signed manifest listing each installable artifact's SHA-256:

curl -s https://partner.gurupras.me/download/latest/update-manifest.json \
  | jq -r '.manifest.artifacts[] | "\(.sha256)  \(.url | split("/") | last)"'

If you installed from a package repository or from Homebrew there is nothing to check by hand: your package manager verified the signature before it installed anything, and refuses anything it cannot authenticate. To confirm you are trusting the right repository key, compare its fingerprint against the one the repository publishes:

curl -fsSL https://partner.gurupras.me/download/repo/apt/current/setup/FINGERPRINT
gpg --show-keys --with-fingerprint /usr/share/keyrings/partner-archive-keyring.gpg

Compare it against your download with sha256sum (Linux) or Get-FileHash (Windows). Partner does this check automatically for self-updates: it refuses to apply an artifact whose hash or signature does not match.

The portable builds are not update targets and are not listed in that manifest; their SHA-256 is in latest.json alongside every other published file.