Readiness checklist (planned)
Planned. Self-hosted deployment is not available yet. The installer's preflight will run these same checks and change nothing; each result is pass, warn or fail with the reason, and the install will not continue past a fail. The commands here are standard Linux and work today, so you can prepare the machine now.
Run them on the machine you intend to use.
1. Operating system
Supported: Ubuntu 22.04 or 24.04 LTS, Debian 12, on x86-64.
cat /etc/os-release
uname -m # expect x86_64
2. CPU, memory and disk
nproc # CPU cores
free -h # memory
df -h /var/lib # free space where the data will live
lsblk -d -o NAME,ROTA,SIZE # ROTA 0 means SSD
Compare against Planning. A spinning disk is a warning, not a fail.
3. The clock
Licence answers carry a time, and the product refuses one that is far from your clock. If the clock is wrong you get "your clock is off by N minutes", not a vague licence error.
timedatectl status # "System clock synchronized: yes", NTP service active
If it is not synchronized, enable time sync (sudo timedatectl set-ntp true) or point chrony at your internal time source.
4. Ports
The application listens on one port (8787 by default, on localhost unless told otherwise) and sits behind a reverse proxy on 443.
ss -ltn '( sport = :443 or sport = :8787 )' # expect no output: both are free
5. Outbound access to Provantix
The deployment calls out; nothing calls in. It needs outbound HTTPS (port 443) to:
| Host | For |
|---|---|
| app.provantix.tech | the hourly licence beacon and activation |
| get.provantix.tech (planned) | downloading and upgrading releases |
curl -sS -o /dev/null -w "%{http_code}\n" https://app.provantix.tech/health # expect 200
If your network requires a proxy, test through it and note the address:
curl -sS -x http://proxy.corp.example:3128 -o /dev/null -w "%{http_code}\n" https://app.provantix.tech/health
If TLS inspection re-signs this traffic, your inspection certificate must be trusted by the machine, and you must tell us: the licence check is signed end to end and does not depend on the connection, but a broken connection looks like a missed beacon.
6. DNS and certificate
You need a hostname on your own domain that people and agents will use (written <your-domain> in this section; for example provantix.yourcompany.com) and a certificate for it. See Domains and TLS.
getent hosts <your-domain> # resolves to the machine (or its load balancer)
7. The database
Either let the installer set up PostgreSQL on the machine, or supply your own. Your own PostgreSQL must:
- support the
vectorextension (pgvector). The product will not start without it; - have an application role that can create databases, because each organization is stored in its own database;
- be reachable from the machine, with a connection string you can give the installer.
psql "postgres://app_role:***@db.corp.example.com:5432/postgres" -c "CREATE EXTENSION IF NOT EXISTS vector;" -c "SELECT rolcreatedb FROM pg_roles WHERE rolname = current_user;"
Expect the extension to be created (or to already exist) and rolcreatedb to be t.
8. Mail
A relay the machine can reach, with credentials and a sender address. See Email.
nc -vz smtp.corp.example.com 587
9. Identity provider
An application registration in your provider, with the redirect address you will use. See Sign-in and SSO.
10. Backups
Where backups will go and who will test a restore. See Operations.
Result
When every line passes, go to Install. Keep the output: the installer saves its own preflight report, and it can be sent with a support bundle.