Deployment
One command. About ten minutes.
A single command brings up the database, both front ends and an HTTPS proxy on your own server. Step-by-step instructions come with your licence.
Before you start
What you need
A Linux server
Any mainstream distribution, any provider, any region. Fresh is best.
Two DNS records
One for your client portal, one for your admin panel.
A licence key
Issued instantly on the free plan, with no card.
About ten minutes
Most of it spent waiting while images download.
How it goes
From nothing to invoicing
- 1
Take a licence key
Create an account and take a licence. The free plan issues one instantly with no card. You nominate your client portal domain and admin domain at this point.
- 2
Point two DNS records at your server
One A record for your client portal and one for your admin panel, both pointing at a fresh Linux server. Certificates are issued for both during deployment.
- 3
Run the deployment command
A single command sets up the whole stack: database, cache, API, both front ends and an HTTPS proxy. The exact command is in your account documentation.
- 4
Create your first staff account
Open your admin domain and complete the setup wizard, then add your mail settings, payment gateways, products and prices from the admin panel.
Day two
Running it afterwards
Routine operations are single commands rather than runbooks. Each one is documented in your account, with the exact syntax and what it changes.
- Status and logsSee what is running and tail the whole stack.
- UpdateRe-check the licence and upgrade in place.
- Backup and restoreTake an encrypted backup, or restore one.
- Health checksConfirm the install is behaving before you need it to.
The technical documentation lives in your account
Deployment commands, the command-line reference, upgrade and rollback procedures and the migration guide are published to licence holders rather than to the open web. Detail about how an install is laid out helps an attacker and does nothing for a buyer.
- Deployment guideThe command, the prerequisites and the wizard, step by step.
- Command referenceEvery day-two operation with its exact syntax.
- Upgrades and rollbackHow to move versions safely, and back again.
- Migration guideRunning the WHMCS importer and reading the dry run.
Questions
Deployment, answered
Where do I get the installation instructions?
In your account. Deployment steps, the command reference and upgrade procedures are documented for licence holders, and the free plan issues a licence instantly with no card.
Why is the command not published here?
Operational detail about how an install is laid out is useful to an attacker and of no use to a buyer. It stays with the people running the software.
What are the server requirements?
A Linux server with root or sudo access. Prerequisites are handled during deployment, so nothing needs to be installed by hand beforehand.
How do I update it later?
A single command re-checks your licence and upgrades in place, rebinding to your domains if you changed them in the portal. The procedure is in your account.
Can I run it behind my own reverse proxy?
Yes. The bundled proxy handles HTTPS out of the box, and the configuration can be adjusted if you already terminate TLS elsewhere.
Can I move it to another server later?
Yes. Take a backup, deploy on the new machine and restore, then move the licence to the new server from your portal account.
Get your free licence key
Twenty-five clients, one staff account, the whole billing engine. It does not expire.