Quartermaster Companion

Quartermaster Companion is a self-hosted web app for the Quartermaster mobile app that discovers services, prepares encrypted setup transfers, and optionally…

  • Infrastructure
  • Tools & Utilities
Quartermaster Companion is a self-hosted web app for the Quartermaster mobile app that discovers services, prepares encrypted setup transfers, and optionally displays a Docker dashboard for homelab monitoring.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

63/100 Good

Maintained
84last commit 23 days ago
Popular
3661 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
84no serious findings, 1 minor, CI, tests, new single-developer project

Based on 4 of 5 factors.

Availability: platform listings confirmed 9 days ago, links checked 18 days ago

GitHub stars
61
Open issues
0
Last commit
2026-10-29
Latest release
v0.1.12
License
MIT
Activity
declining

Checked 6 days ago - source: GitHub (lewlew-glitch/qm_companion)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Unraid setup For Unraid, create the dedicated qm-companion Docker network first, then install the separate qm-socket-proxy and Companion on it with the same proxy key. source
  • Setup transfer behavior The short-lived encrypted setup transfer does not route ongoing app traffic; afterward, Quartermaster connects directly to the local and away addresses saved for each service. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Should I mount the whole app-data directory for service configs?

No. Mount individual service config files only, not the app-data parent directory.

How should I handle .env during an upgrade?

Existing installations must keep their current .env and SECRET_KEY. Skip creating new secrets during an upgrade.

Which port should I expose for the Companion web UI?

Expose port 8787 and open the address on that port to claim the owner account. If SETUP_TOKEN is not set, the first-run token is written to the log while no owner exists.

How does Unraid provide Docker access without exposing the Docker socket to Companion?

Use separate qm-socket-proxy and qm-companion entries. Create the dedicated qm-companion Docker network first, then install both on it with the same proxy key.

Does the Quartermaster phone app route traffic through Companion after setup?

No. The standard setup transfer does not route app traffic through Companion; after setup, Quartermaster connects directly to the local and away addresses saved for each service.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads