Secure a self-hosted installation
Protect access and secrets
Section titled “Protect access and secrets”- Use HTTPS for the application, restrict direct access to internal services, and keep the host, container images and proxy current.
- Limit access to the host, deployment files, secret store, database and backups. Never put session, integration, admin, database or registry credentials in frontend code or support tickets.
- Use separate strong session and integration secrets. Changing the integration secret makes previously stored integration credentials unreadable; plan rotation and recovery before changing it. Session-secret changes invalidate existing signed sessions.
- Configure signup, user roles and authentication for your organization. Public project keys are for SDK ingestion; secret and admin credentials must stay on the server or in an authorized secret store.
- The Compose application services run as a non-root user with read-only root filesystems and dropped capabilities. These defaults do not replace host, network and access controls.
Protect report data
Section titled “Protect report data”Reports and media can contain sensitive information and are not encrypted by the application at rest. Use encrypted storage and encrypted, access-controlled backups; apply retention policies appropriate to your data. Redaction is best-effort and does not guarantee that every sensitive value or image region is removed. Review captured content and configure privacy controls for your application.
Replay sharing is off by default. Enabling it requires a dedicated HTTPS embed origin on a different hostname from the configured application and API URLs, plus explicit opt-in. With Caddy, the supplied replay-site example must also be configured and enabled; the origin setting alone does not publish it. Disabling sharing blocks access and creation but does not revoke existing grants. Rollback or restoration requires additional safety steps; see upgrades and recovery.