How to Self-Host Cockpit
Cockpit browser-based Linux administration console for inspecting services, logs, storage, networking, accounts, updates, and virtual machines. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Cockpit is a good fit
Choose Cockpit when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install the distribution package and enable the Cockpit socket. Access it over a trusted network or VPN and keep normal Linux authentication policies in force.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Cockpit manages the host rather than owning a large application database; back up host configuration and the services it controls.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
This is a privileged administration surface. Avoid public exposure and require strong operating-system accounts.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
