Self-hosting ProofTrail

ProofTrail runs on your own server, as one Docker image. Your compliance data, your evidence and your staff's details stay there; the only thing that leaves is a daily license check.

What you need#

• A Linux server on x86_64 with Docker and Docker Compose.
• A domain or subdomain for ProofTrail, such as compliance.example.com, behind a reverse proxy that serves it over HTTPS.
• An SMTP account, so ProofTrail can send sign-in links, task reminders and policy requests.
• A license key. One key covers a production and a staging installation.

ProofTrail keeps its data in SQLite, its queue and its cache in the same database, so there is no database server, Redis or other service to run beside it.

The pages of this guide#

• Install ProofTrail: the compose file, the .env file and the first start.
• Your license key: activating it, moving it and what happens when it lapses.
• Configuration: mail, backups and health alerts.
• Upgrades: moving to a new version.
• Backups: what is backed up and how to restore it.

Want to look around first? The demo runs on a fictional company, with no account to create.