Wholly CryptoMerchant releases
Stable channel Loading release…

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.

Ubuntu 24.04 LTSx86-64 / amd64Run as root

Install on a fresh VPS

One command

Point console.example.com, pay.example.com and api.example.com at your server. Allow ports 80 and 443.

bash <(curl -fsSL https://releases.whollycrypto.com/setup_wholly.sh)

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. Other Linux versions and ARM64 are not packaged yet.

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 yours
whollycrypto update

Checks the signed stable release, takes a recovery backup, then updates and checks application health. Use whollycrypto update --check to check without installing.

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.

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.