Self-hosting means running an application or service on equipment you manage, rather than relying entirely on a provider to operate it for you. That can offer more control over the setup, but it also means taking responsibility for keeping the service available, maintained and appropriately protected.
It does not automatically make a service more private, less expensive or safer. Those outcomes depend on the software, configuration, network exposure, maintenance and the time required to look after it.
Before putting a service online
- Who needs access, and how will you control it?
- How will you install updates and notice when something needs attention?
- What is backed up, where is the backup stored, and have you tested restoring it?
- Does remote access expose a management interface or other sensitive part of the system?
- What happens when the device, power, internet connection or service is unavailable?
- Will maintaining it still be worthwhile after the initial setup?
For a specific example of the responsibilities involved, Docker’s Engine security documentation discusses daemon access, container configuration and other security considerations. It is technical product documentation, not a claim that containers or self-hosting are secure by default.
This page began as notes for a possible Smart Tech for Real People topic. It is not a book announcement, and I may never publish a book about it. See the books currently available for confirmed titles.