Your server.
Your payments.
Install Wholly Crypto on your own VPS. A lightweight merchant console, multi-chain checkout and payment API — without Docker or local blockchain nodes.
Install on a fresh VPS
One commandPoint merchant.example.com, pay.example.com and api.example.com at your server. Allow ports 80 and 443.
bash -c 'wholly_setup=$(curl -fsSL --connect-timeout 10 --max-time 60 https://releases.whollycrypto.com/setup_wholly.sh) || wholly_setup=$(curl -fsSL --connect-timeout 10 --max-time 60 https://raw.githubusercontent.com/whollycrypto-com/whollycrypto/main/setup_wholly.sh) || exit 1; exec bash -c "$wholly_setup" -- "$@"' --Setup asks for your domain and email, then installs PostgreSQL, Nginx, HTTPS and the merchant application. Each installation gets its own keys and credentials.
Options and requirements
Recommended: at least 2 GB RAM and 3 GB free disk, plus room for your data and backups. Supports Ubuntu 22.04+, Debian 12+, Fedora 42+, Rocky/Alma/RHEL/Oracle/CentOS Stream 9–10, openSUSE Leap 16/Tumbleweed and Arch. Requires systemd 247+ and Python 3.9+. ARM64 and Alpine/OpenRC are not supported.
Use setup_wholly.sh --check to check compatibility without installing. Setup uses native packages, enables official EPEL on Enterprise Linux, and keeps SELinux enabled. Existing database clusters are never upgraded automatically.
DNS records must point directly to the VPS, including any IPv6 records. Disable CDN/proxy mode for initial setup. Your firewall rules are not changed.
bash <(curl -fsSL https://releases.whollycrypto.com/setup_wholly.sh) \
--domain example.com --email admin@example.com --yes
--yes accepts installation and the Let's Encrypt subscriber agreement. Use --resume to resume an interrupted fresh setup. Existing installations must use the updater.
After setup, read /root/whollycrypto/config/setup-credentials.txt for your HTTP Basic login, then create your console administrator account.
Update your merchant
Wallets and settings stay yourswhollycrypto updateChecks the signed stable release, takes a recovery backup, then updates and checks application health. Use whollycrypto update --check to check without installing.
From 0.1.20, signed downloads automatically fall back to GitHub Releases. Older installations must update once first. Both hosts serve the same verified merchant files.
Update with a script
bash <(curl -fsSL https://releases.whollycrypto.com/update_wholly.sh)This uses the same installed CLI and pinned release key. Updates briefly pause checkout; database-changing failures never trigger a blind database rollback.
If this host is offline, use the installed whollycrypto update command or the GitHub update launcher.
Release files
Signed merchant binary package
The initial setup script is trusted over HTTPS. Download and inspect it first if required by your security policy. Installed updates verify signed metadata and checksums using a pinned public key. Recovery backups contain sensitive data and should also be kept securely off-server.