Self-hosted LoadoutHQ

This customer handbook is the supported operations reference for customer-managed LoadoutHQ installations. The production path is a GitOps-managed Helm release using the chart published as an OCI artifact.

Start here

1. Confirm prerequisites and ownership.
2. Prepare configuration and Secrets.
3. Install through GitOps.
4. Activate the instance.
5. Configure the first administrator and OIDC.
6. Review the security guidance.
7. Adopt the operations runbook.
8. Review troubleshooting and support collection.

Support boundary

LoadoutHQ supplies the API and web images, Helm chart, schema migrations, and product documentation. The customer operates Kubernetes, ingress, DNS, TLS, PostgreSQL, S3-compatible storage, backups, registry credentials, monitoring, and identity-provider availability. Valkey may be externally operated or installed through the optional official chart dependency; either mode remains part of the customer's operational responsibility.

The chart deploys no PostgreSQL or object-storage service. It deploys a single-instance Valkey only when valkey.enabled=true. Official production images require a valid offline vendor-signed license. License validation makes no outbound network request.