The other comments you received relies on 3rd parties and/or tunneling traffic via others, which may or may not impact the performance/latency negatively (depen

The other comments you received relies on 3rd parties and/or tunneling traffic via others, which may or may not impact the performance/latency negatively (depending on what you're trying to achieve). If you want to self-host a solution, few things to keep in mind: - Rate-limit "heavy" (RAM, CPU, I/O) processes that can be externally triggered via HTTP calls or similar (if you have a HTTP endpoint for regenerating a cache or something like that, make sure it can only be called max once per hour, and so on) - Setup fail2ban, and things like mod_evasive if you're using Apache (I'm sure Caddy/nginx have similar solutions) - Only expose what you really want to with iptables Ultimately, unless you're hosting something really popular or controversial, you don't really need to be scared about being ddosed. People don't spend resources just ddosing random stuff without a reason for it, and unless it's popular/controversial, you just won't get hit by anything but random port scans/vulnerability scans.