Feature
Score history in Postgres
Every uploaded Build and its Runs are stored in a Postgres database you own, so trends survive redeploys.
The LHCI server stores each Build, and the Runs inside it, in Postgres instead of on the container’s own disk. Containers are rebuilt and replaced; the score history is not.
The server creates its tables itself on first boot, so there is no migration step. SSL is on by default for a hosted database and can be turned off with LHCI_DATABASE_SSL=false for a local one.
The dashboard compares each Build against the Project’s base branch.
More features
All features →- 01
One gate for every route
Server basicAuth protects the dashboard, registration and the upload endpoint with one username and password.
- 02
Registration with two tokens
lhci-toolkit register creates a Project and prints its Build token for CI and an Admin token you keep.
- 03
Uploads from any CI pipeline
Run npx @lhci/cli autorun with three secrets and each pull request uploads its report.