Install kudde.

kudde is not on Google Play. Each release is a signed APK on GitHub, and Obtainium installs it and tells you about updates.

What you need

  • An Android phone on Android 12 or newer (arm64).
  • herdr-core 0.1.15 or newer on a Linux or WSL machine, installed as the user your agents run under:

    curl -fsSL https://releases.herdr.dev/core/install.sh | sh

    The herdr terminal tool is a different program; kudde does not need it.

  • An OpenSSH server on that machine that the phone can reach, for example over Tailscale. Tailscale SSH does not work, as it ignores the phone key: use the machine’s LAN address, or an OpenSSH port Tailscale does not take over.
  • For alerts: an ntfy server, the ntfy app on the phone, and kudde-push on each machine.
  • To install and update: Obtainium, or adb on a computer.

With Obtainium

Get Obtainium

Obtainium is not on Google Play either. On the phone, open its releases, download app-arm64-v8a-release.apk from the newest release and open it. Android asks to let your browser install apps; allow it.

Add kudde

  1. In Obtainium, tap Add App and enter https://github.com/enhulsman/kudde. The defaults are fine.
  2. Tap Install. Android asks to let Obtainium install apps; allow it.
  3. Leave background installing off. Obtainium may tell you about an update; you install each one by hand, after checking it.

If Obtainium’s checks fail, GitHub is limiting how often it may check without a token. Create a fine-grained personal access token with access to public repositories and nothing else, and add it under Obtainium’s GitHub source settings.

When Android stands in the way

Play Protect

Play Protect may show “App scan recommended”. Scanning is fine, as the APK is public, or choose Install without scanning under More details. With Identity Check on, that asks for your fingerprint or face.

Advanced Protection

On Android 16, Advanced Protection allows only apps from Google Play and the stores that came with the phone, so it blocks Obtainium and anything it installs. Turn it off to install, or install from a computer with adb.

From a computer with adb

  1. From the latest release, download kudde-<version>.apk and SHA256SUMS, and check them.
  2. Turn on USB or wireless debugging on the phone, then run:

    adb install --user 0 kudde-<version>.apk

    --user 0 keeps it out of a work profile or Private Space.

Updates go the same way, with adb install -r --user 0.

Checking a release

On the first install, check that the APK is the one this project signs. On a computer, in the folder with the downloads:

sha256sum --check --ignore-missing SHA256SUMS
apksigner verify --print-certs kudde-<version>.apk

apksigner comes with Android’s build tools. Its “Signer #1 certificate SHA-256 digest” must be:

Release signing certificate SHA-256: c64a4bae52e0e8f840dcc670d94dac9e3f6986f509c2489e5b48f8b88157e8e6

The same value is kept in the repository, in docs/release-signing-fingerprint.txt, and the release workflow publishes nothing that does not match it.

After the first install, Android itself refuses an update signed with any other key. Before installing an update, open the release on GitHub: its notes name the commit it was built from. Open that commit, and GitHub lists main among the branches that contain it. If it does not, do not install the update, and open an issue.

The full install guide on GitHub

Next, add a machine.

Set up kudde