Self-hosted deployment: overview (planned)

Status: planned, not available yet. This section describes how Provantix will run on a machine you provide, what to prepare, and how it is licensed, connected and operated. No date is promised. If you need this, talk to us before relying on it.

Your domain, not ours. A self-hosted deployment runs on a hostname on your own domain. Wherever this section shows <your-domain>, replace it with that hostname; every address with <your-domain> in it is an example of the shape, not a value to copy. The only Provantix addresses a deployment contacts are the licence and download hosts listed in Readiness.

How to read the commands. Standard Linux commands (timedatectl, ss, curl, journalctl, psql) and the settings written in capitals (LEDGER_PUBLIC_URL, SMTP_HOST, and so on) work as written. Commands that start with provantix or ./install.sh are the planned installer interface: the names and options may change before release, and each page says so where it matters.

What it is

A self-hosted (customer-run) deployment is the same Provantix product running on a virtual machine that you provide and control, connected outbound to provantix.tech for your licence. You choose where it runs: your data centre, your cloud account, your region. Your records stay on your machine.

It is for organizations that must keep audit evidence inside their own boundary. If you can use the hosted service, it needs less from your team.

The path, in order

  1. Planning: decisions and sizing before you ask for a machine.
  2. Readiness: the checklist the installer's preflight also runs.
  3. Install: download, verify, preflight, install, first sign-in, self-test.
  4. Licensing: activation, the hourly beacon, warnings, moving a machine.
  5. Domains and TLS: the public address, the reverse proxy, certificates.
  6. Sign-in and SSO: your identity provider and your administrators.
  7. Email: your mail relay.
  8. Connecting agents: emitters, the SDK, OpenTelemetry, collectors.
  9. Alerts: email and webhooks to your own systems.
  10. Operations: health, logs, backup, upgrade, support bundle, uninstall.

What is decided

  • A virtual machine, not Kubernetes. Ubuntu 22.04 or 24.04 LTS, or Debian 12, on x86-64. A Kubernetes chart may come later.
  • A signed download. Each release is a versioned archive with a checksum and a signature that the installer verifies before it installs anything.
  • Your own sign-in and mail. Your identity provider (OpenID Connect) and your SMTP relay. Provantix-managed Google sign-in and billing screens do not exist in a customer-run install.
  • Your keys. The deployment creates its own signing key on the machine; your exports and roots are signed by your deployment, not by Provantix. See How verification works.
  • Priced per active agent, the same unit as the hosted plans.
  • No restrictions on what you run. Provantix does not cap agents, records, retention or features in a self-hosted deployment: using more than you bought is billed, never refused, and there is no queue or volume limit in the SDK or collector. The one control is licence status: a lapsed or revoked licence stops telemetry (HTTP 402) and nothing else; verifying and exporting your evidence keeps working.
  • Your domain, your sign-in. The deployment runs on your hostname and signs people in with your own OpenID Connect provider (Okta, Keycloak, AD FS, Ping, Auth0, Entra, Google Workspace and others). See Sign-in and SSO.
  • No AI Insider in the first release.

What Provantix can and cannot see

There is no way in for Provantix: no remote login, no shell, no tunnel and no standing account. The installer gives Provantix staff no access, and Provantix's own operator console only knows what your deployment's beacon reports. If you want someone from us to look at your system, you open a screen-share or grant access yourself, for that session.

What we receive:

  • the hourly beacon: deployment id, a rising sequence number, the time, the product version, counters (active agents and record counts) and a salted hash that lets us notice a copied machine. No records, no content, no names;
  • sanitized usage and error logs: counts, timings, versions and error classes, built from a fixed allow-list of fields so that nothing else can pass. The allow-list is reviewed in writing by our owner, and by your security team before go-live;
  • a support bundle that you generate and send yourself when you want help: versions, health, configuration with secrets removed, and counters, never records.

What is not in the first release

Bring-your-own-key encryption, the AI Insider, Kubernetes, and sites with no outbound access at all (those need an offline licence file, planned later).