Planning a self-hosted deployment (planned)
Planned. Self-hosted deployment is not available yet. Sizes below are a provisional starting point, to be replaced by tested figures before release.
Decide these before you ask for a machine. Most delays come from the last four.
1. Who is it for, and how many agents?
Provantix is priced and sized by active agents: agents that sent records in the billing period. Write down today's count and what you expect in a year. Using more than you bought is billed, never refused, so a low estimate costs you money, not evidence.
2. One machine or more
The first release is one virtual machine running the application and its database. That is enough for most organizations. If your policy requires the database on a separate, managed PostgreSQL, say so early: it must support the vector extension and let the application's role create databases (each organization gets its own database). Both are on the readiness checklist.
3. Sizing (provisional)
What drives size is records, not people. Plan disk from this: records per day times your retention period. Evidence is kept for years, so disk is the figure that grows.
| Active agents | Starting point |
|---|---|
| up to 50 | 4 vCPU, 16 GB memory, 200 GB SSD |
| 50 to 250 | 8 vCPU, 32 GB memory, 500 GB SSD |
| more | talk to us; this is where a separate database host helps |
Put the data on its own volume so it can grow and be backed up on its own. The installer's preflight will report CPU, memory, disk space and disk type against this table.
4. Where it lives and who can reach it
- Where: your data centre or your cloud account, in the region your policy requires. Provantix does not choose.
- Who reaches the web app: people on your network, or through your VPN. It does not need to be reachable from the internet.
- Who sends telemetry to it: your agents and collectors, from wherever they run. They need a network path to it.
- What it reaches out to: provantix.tech, for the licence (see Readiness for the exact list). If your network forces an outbound proxy, you need its address and any credentials.
5. People and decisions to line up
| Item | Why it comes early |
|---|---|
| An administrator who owns the machine | Installs, upgrades and backups are theirs. |
| A hostname and a TLS certificate | See Domains and TLS. Certificates are often the slowest request. |
| An identity provider and an application registration | See Sign-in and SSO. |
| A mail relay and a sender address | See Email. Sign-in codes and invitations arrive by email. |
| A backup target and a restore test | See Operations. |
| Your security team's review of the log allow-list | Required before go-live. See Overview. |
6. A rough timeline
Most of the time is waiting on others: the machine, the certificate, the identity provider and the security review. The install itself is meant to take under an hour once the checklist passes. Start the long requests first.