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) | — (Rosetta works) | ✅ 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 only. Intel Macs work via Rosetta —
Quay.appruns through it transparently — but a native universal2 DMG that covers both arm64 and x86_64 in a single installer is on the roadmap.
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). Apple notarisation is in progress —
until the next release ships notarised builds, macOS shows a “cannot
verify the developer” warning on first launch. The xattr step strips
the quarantine bit that triggers it. Alternative: right-click
Quay.app → Open → Open in the warning dialog.
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. It ships pre-built starting
with the next desktop release. Until then the desktop app’s
in-process scheduler covers the “back this up while my Mac is open”
path.
For early access to a v0.1 CLI build, file a request via Settings → Feedback in the app. Once they ship: see CLI overview and CLI install for 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”Per-release SHA-256 sidecars land alongside the artifacts as the release pipeline matures. Until then verify by checking the developer-id signature instead:
codesign --verify --deep --strict --verbose=2 /Applications/Quay.appspctl -a -t exec -vvv /Applications/Quay.appBoth should report Developer ID Application: MUHAMMAD ZAID TAUFIQ YASYAF (HPJ77R28B5). If they don’t, the app was tampered with after download — re-download.