Domains and TLS (planned)
Planned. Self-hosted deployment is not available yet. The settings named in capitals are what the product reads today; the proxy configuration is standard and works as written.
The public address
Pick one hostname for the whole deployment, on your own domain. Throughout this section <your-domain> stands for it: replace it with your real hostname, such as provantix.yourcompany.com. It is never provantix.tech. People open it in a browser and agents send telemetry to it. Set it once:
LEDGER_PUBLIC_URL=https://<your-domain> # example: replace with your own hostname
It is used in links in emails, in sign-in redirects, in the setup commands shown for new agents, and as the redirect address you register with your identity provider. If it is wrong, those all point to the wrong place.
It must be reachable by the people and the agents that use it, from inside your network. It does not need to be reachable from the internet.
The reverse proxy
The application listens on a local port (PORT, default 8787, on HOST, default 127.0.0.1). Put a reverse proxy in front of it that terminates TLS on 443. Do not expose the application port directly.
An nginx example:
server {
listen 443 ssl;
server_name <your-domain>;
ssl_certificate /etc/ssl/provantix/fullchain.pem;
ssl_certificate_key /etc/ssl/provantix/privkey.pem;
# Batches can be up to 10 MB; leave headroom.
client_max_body_size 12m;
location / {
proxy_pass http://127.0.0.1:8787;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 60s;
}
}
server {
listen 80;
server_name <your-domain>;
return 301 https://$host$request_uri;
}
The installer does not choose your proxy. If you use a load balancer or an existing gateway, give it the same upstream and the same body-size limit.
Trusted proxies
The platform records the client's address for rate limits and audit. It trusts X-Forwarded-For only when the request comes from a proxy you name, and then takes the right-most address that is not itself a trusted proxy. A request from anywhere else cannot spoof it.
LEDGER_TRUSTED_PROXIES=127.0.0.1,10.20.0.5
Comma-separated addresses or CIDR ranges: your reverse proxy, and any load balancer in front of it. If you leave it empty, every client appears to come from the proxy, and limits apply to all your users together.
Certificates
Use a certificate from your own certificate authority or a public one, for the hostname above. Browsers and agents must trust it.
- Browsers use your organization's trust store, as for any internal site.
- Node agents that send telemetry over TLS to an internal authority must trust it too. Node does not use the system store by default:
export NODE_EXTRA_CA_CERTS=/etc/ssl/corp-root-ca.pem
Check from an agent's machine:
curl -sS https://<your-domain>/health
openssl s_client -connect <your-domain>:443 -servername <your-domain> </dev/null 2>/dev/null | openssl x509 -noout -subject -dates
Renew before expiry: an expired certificate stops people and agents, and a stopped agent queues its batches, so renew on a calendar, not on a failure.
The session cookie
In a customer-run install the session cookie belongs to the exact hostname and is not shared with any other site on your domain. This is deliberate: a cookie shared across corp.example.com would be sent to every internal application there. If you want one sign-in across several internal hostnames, set the parent domain explicitly and understand what shares it:
LEDGER_COOKIE_DOMAIN=corp.example.com
Links and the Docs button
The Docs link in the app points to the public documentation by default. If your browsers cannot reach it, point it somewhere you host, or leave it:
LEDGER_DOCS_URL=https://docs.corp.example.com
Without outbound access to provantix.tech from browsers, the public docs will not open from inside the app. An offline copy of the docs is planned.
Connecting an AI assistant (MCP)
If you use the MCP connector, it needs its own resource address, usually a separate hostname:
LEDGER_MCP_RESOURCE=https://mcp.corp.example.com
It is optional; leave it unset and the MCP endpoints stay off. See Connect your AI assistant.
Content security
In a customer-run install the browser security policy leaves out the payment and analytics services that the hosted service uses. Nothing to configure; mentioned so your security team is not surprised that it is stricter.