docs
On this page

Install Polysia on a server

Requirements

  • Ubuntu 22.04 or 24.04, 2 vCPU / 4 GB RAM / 40 GB disk recommended (sizing: see the Capacity card in the dashboard)
  • a domain with an A record pointing to the server (e.g. pay.example.com)
  • 2–3 Polygon RPC URLs (e.g. from Alchemy), the PolysiaFactory address and its deploy block
  • SSH access with a key

Install

curl -fsSLO https://github.com/sirkyawsan/polysia-releases/releases/latest/download/install.sh
sudo bash install.sh

The installer:

  1. downloads the release from GitHub Releases and verifies the Ed25519 signature of SHA256SUMS with the Polysia release key embedded in the script, then every SHA-256 — before anything is installed;
  2. installs Docker, asks for the domain, the Let's Encrypt e-mail, the chain settings and the RPC URLs (hidden);
  3. starts PostgreSQL, polysiad and Caddy (automatic HTTPS); only /v1/*, /pay/* and /l/* are public;
  4. prints the link to the setup wizard.

Setup wizard

On your own computer:

ssh -L 8080:127.0.0.1:8080 you@your-server

Open the printed http://127.0.0.1:8080/setup?token=… link:

  1. Owner — user name, password, two-factor authentication.
  2. Wallet — generate the 24-word seed phrase and write it down on paper; re-type three words; choose the vault passphrase. The wizard checks that the Gas Wallet address has never been used. Send ~5 POL to it for gas.
  3. Vault page — unlock with the passphrase and a 2FA code. Sweeps start.
  4. Finish — optional e-mail for security notices.

Use the seed phrase and the Gas Wallet only through Polysia. Never import them into MetaMask, Trust Wallet, SafePal or any other wallet app, and never reuse a seed phrase a wallet app already uses: a payment sent from another wallet takes the transaction nonce Polysia queued and its sweeps and withdrawals fail.

After a restart

Payments keep being received and shown, the API and payment pages work — but sweeps and withdrawals wait until an Owner unlocks the vault (dashboard → Vault). You get an alert after 5 minutes.

Updates

Dashboard → Updates: releases are verified against the release key built into Polysia, the database is backed up first, and a version that does not start is rolled back automatically. Automatic installation of security releases is off by default.

Backups

  • the 24 words (paper, offline)
  • the Docker volume polysia-data (vault, admin key, update backups) and the installer's .env
  • a daily database backup of your own