How it works
From purchase to first login—how your Self-Hosted Pro license is provisioned and how the install email gets you running.
After you purchase Self-Hosted Pro, provisioning and install follow a short, predictable path: license appears in Billing, you assign a domain, Apnotic provisions the license, and you receive an email with a personalized install command and steps. Below is that flow, plus an example of what the email looks like.
From purchase to install
- License in Billing — Under Billing, your new self-hosted license appears.
- Assign a domain — You’re prompted to assign the domain where the app will run. That domain is tied to the license so it can be provisioned.
- Provisioning — Once the domain is set, the license is provisioned.
- Email with install instructions — You receive an email containing your personalized install command and the steps to run it (prepare server, DNS,
docker compose, first admin user).
The install command is unique to your license. It authenticates to the private registry, pulls your docker-compose.yml and .env (with fresh encryption keys), and starts the stack.
Example email (after purchase)
The message you receive is similar to the following. Treat the install command like a secret—anyone with it could deploy against your license context.
Your install command
curl -fsSL "https://license-server/install.sh?license_key=YOUR-LICENSE-KEY" | shKeep this private. This command is personalized to you and your license. Do not share it publicly or in tickets/chat.
Installation steps
- Prepare your server — Use a machine with Docker and Docker Compose installed.
- Configure DNS — Point your chosen hostname (e.g.
pwpush.example.com) to your server’s IP. TLS is set up automatically.- Run the install command above — This will:
- Authenticate with the private Docker registry
- Download your
docker-compose.ymland.envwith fresh encryption keys- Start the application, e.g.
docker compose up -d- Complete setup — Open
https://your-hostnamein a browser and create the first admin user.First user and boot code — First user creation requires a boot code. Find it in the logs:
docker compose logs pwpush-pro
Keep the install command secret. The URL in the email is personalized and grants access to your license context—do not paste it into public channels or support threads without redacting.
Related
- Air-gapped / offline — No
curlor registry on the target host - Getting started checklist — What to do next, in order
- Pro Self-Hosted overview — Plans and features
- System requirements — Docker, CPU, memory
- Configuration — Admin settings after install