Install
Quay ships signed installers for macOS, Windows, and Linux. Latest release is v0.3.1 (auto-fetched from /v1/releases at build time — the URLs below always point at the most recent build).
curl -sS https://license.quay.uncle-z.com/v1/releases | jqPlatform support
Section titled “Platform support”| Platform | Architecture | v0.3.1 (today) | Next |
|---|---|---|---|
| macOS | Apple Silicon (arm64) | ✅ Quay_{VERSION}_aarch64.dmg | ✅ |
| macOS | Intel (x86_64) | ❌ not supported yet | ✅ universal2 DMG |
| Windows | x64 | ✅ Quay_{VERSION}_x64-setup.exe | ✅ |
| Windows | arm64 | — | (under evaluation) |
| Linux | x86_64 (.deb) | ✅ Quay_{VERSION}_amd64.deb | ✅ |
| Linux | x86_64 (.rpm) | ✅ Quay-{VERSION}-1.x86_64.rpm | ✅ |
| Linux | aarch64 | — | ✅ planned |
Minimum versions: macOS 13 (Ventura) · Windows 10 · Ubuntu 22.04 / Debian 12 or any distro with WebKitGTK 4.1+.
macOS (Apple Silicon)
Section titled “macOS (Apple Silicon)”Today’s macOS build is Apple Silicon (M1 or later) only. It does not run on Intel Macs: Rosetta 2 runs Intel apps on Apple Silicon, not the other way round. A universal2 DMG that covers both arm64 and x86_64 is planned.
One-liner install
Section titled “One-liner install”DMG=~/Downloads/Quay.dmgcurl -L -o "$DMG" https://dl.quay.toko.center/Quay_0.3.1_aarch64.dmghdiutil attach -nobrowse -readonly "$DMG"sudo cp -R /Volumes/Quay/Quay.app /Applications/hdiutil detach /Volumes/Quayxattr -dr com.apple.quarantine /Applications/Quay.appopen -a /Applications/Quay.appAbout Gatekeeper
Section titled “About Gatekeeper”The DMG is signed with Developer ID Application: MUHAMMAD ZAID TAUFIQ YASYAF (HPJ77R28B5) and notarised by Apple. On first launch macOS shows the usual “downloaded from the internet” prompt. Click Open.
If macOS still blocks the app (for example after a copy that lost its quarantine data), open System Settings → Privacy & Security, scroll to the Security section, click Open Anyway next to “Quay was blocked”, then confirm with your password or Touch ID. Check the download first with Hash verification below.
Windows
Section titled “Windows”# Download the signed installercurl -L https://dl.quay.toko.center/Quay_0.3.1_x64-setup.exe -o Quay-setup.exeThen double-click. SmartScreen may flag on first run; click “More info” → “Run anyway”.
# Debian / Ubuntucurl -L -O https://dl.quay.toko.center/Quay_0.3.1_amd64.debsudo dpkg -i Quay_0.3.1_amd64.deb
# RHEL / Fedoracurl -L -O https://dl.quay.toko.center/Quay-0.3.1-1.x86_64.rpmsudo rpm -ivh Quay-0.3.1-1.x86_64.rpmWebKitGTK is the only runtime dependency — apt / dnf will pull it.
Verify the install
Section titled “Verify the install”After install, confirm the version:
- GUI: Settings → About — shows the version, bundle id, license status, and a link to the release notes.
- macOS terminal:
Terminal window defaults read /Applications/Quay.app/Contents/Info CFBundleShortVersionString - Linux terminal:
Terminal window dpkg -s quay | grep '^Version' # or `rpm -qi quay | grep Version`
If the version doesn’t match the latest at /v1/releases, run the
Upgrade flow.
CLI (24/7 scheduled backups)
Section titled “CLI (24/7 scheduled backups)”The Quay CLI (quay) is the headless companion that fires scheduled
backups when the desktop app isn’t open. Pre-built binaries are
available for macOS, Windows and Linux: see CLI overview
and CLI install for the download links and the
launchd / systemd unit setup.
Where Quay puts its data
Section titled “Where Quay puts its data”Useful for support questions + uninstall:
| Path | macOS | Linux |
|---|---|---|
| Connections + projects | ~/Library/Application Support/com.unclez.quay/connections.json | ~/.config/quay/connections.json |
| Schedules | same dir, schedules.json | same dir, schedules.json |
| Licence + activation | same dir, license.json | same dir, license.json |
| Settings | same dir, settings.json | same dir, settings.json |
| Default backup location | ~/Documents/Quay Backups/ | ~/Documents/Quay Backups/ |
Connection passwords stay plaintext in connections.json (locked
decision). The file is mode 0600 by default.
Upgrade
Section titled “Upgrade”The desktop app self-checks against the licence-server release manifest on launch and surfaces an “Update available” badge. Manual upgrade is the same as install — overwrite the previous build (the data dir survives untouched).
Uninstall
Section titled “Uninstall”| OS | Command |
|---|---|
| macOS | rm -rf /Applications/Quay.app (data dir kept) |
| macOS, full wipe | add rm -rf "~/Library/Application Support/com.unclez.quay" "~/Documents/Quay Backups" |
| Windows | Settings → Apps → Quay → Uninstall |
| Debian | sudo apt remove quay (sudo apt purge quay to also drop config) |
| RHEL | sudo rpm -e quay then rm -rf ~/.config/quay for full wipe |
The CLI is sudo rm /usr/local/bin/quay plus its launchd plist /
systemd unit if you set one up.
Hash verification
Section titled “Hash verification”Check that the file you downloaded is the one we published, before you open it. Compute the SHA-256 and compare it with the table.
shasum -a 256 ~/Downloads/Quay_0.3.3_aarch64.dmg # macOSsha256sum Quay_0.3.3_amd64.deb # LinuxGet-FileHash .\Quay_0.3.3_x64-setup.exe -Algorithm SHA256 # WindowsSHA-256 for v0.3.3:
| File | SHA-256 |
|---|---|
Quay_0.3.3_aarch64.dmg | f5d03604ca141acb10c5e0aada7eeef6af576a25ffa95e910802ca4408c52ce9 |
Quay_0.3.3_x64-setup.exe | 3541d9cad66d187af2024b880fc860d23daada505cbf40a2da604a8de9d4a779 |
Quay_0.3.3_amd64.deb | 16f486f80fc5268fb2115a023a3a7a591199f364b82834de3b5888db13704080 |
Quay-0.3.3-1.x86_64.rpm | 08e9f5b8014dcdb593bd6ae4d4765462055ff89d7f1dd68c0e2749b6aa223711 |
If the hash differs, delete the file and download it again.
After you copy the app to /Applications, you can also check the
developer signature on macOS:
codesign -dv --verbose=2 /Applications/Quay.app 2>&1 | grep -E "Authority|TeamIdentifier"codesign --verify --deep --strict /Applications/Quay.app && echo "signature OK"You should see Authority=Developer ID Application: MUHAMMAD ZAID TAUFIQ YASYAF (HPJ77R28B5) and TeamIdentifier=HPJ77R28B5. To ask Gatekeeper
directly, run spctl -a -vvv -t install on the DMG: it should report
accepted with source=Notarized Developer ID.