While self-hosting can save money in some aspects, it also involves costs, such as for the computing hardware itself, but also the electricity costs, which some advanced users have noted can be unexpectedly high. If users access their self-hosted services on a domain they own, there is usually a cost involved in registering the domain. Performance can be faster on local hardware due to the lower latency, but it can sometimes be slower on self-hosted hardware, particularly if attempting to host on under-powered devices such as
single-board computers like
Raspberry Pi, which can struggle to run intensive processes involved in speech-to-text algorithms, video encoding and similar applications. Security must be considered when self-hosting software exposed to the public internet. Making resources on a home network remotely accessible usually involves
port forwarding, setting up encryption methods like
HTTPS, and other networking approaches which if not configured correctly, could become an
attack surface for hackers and thieves. It is also recommended to back up any self-hosted data to a second location, potentially offsite, to ensure all data isn't lost in case of a fire, flood or other disaster that could destroy hardware in a home. Self-hosting software often has a steeper
learning curve than competing software because of the need to learn about computer networking, security, and software configuration on environments such as
Linux and the
command line. This can require more time investment than paid alternatives. ==Examples==