Selfhosted

You're being downvoted because you're asking another "I want everything, but works exactly to my needs, only the way I want it, and cheap." kind of question.

Cloudflare exists for a reason, as does every other DDOS mitigation platform. If there was a better or cheaper solution, they would be out of business already.

Best you're probably going to do for self-hosting is going to be blackholing abusive connections, but even then you're only going to be able to mitigate so much. Differentiation of mass amounts traffic still takes a massive amount of time and compute.

I wouldn't worry about DDOS attacks at all.

People simply don't care about whatever small website you plan on hosting. Unless it's something extremely controversial and you gain a lot of exposure suddenly.

It's worth worrying about if you ever get big but until then just forget it.

I.E. do something about it when/if it happens and not before. A ddos is fairly harmless unless you need to stay up for some reason (and you don't need to stay up).

You don't have to worry about DDoS:

• DDoS is an advanced technique and the people who can do that spend a lot of time and effort putting malware on machines that can be ordered to perform DDoS on command. They usually sell that attack capability and it ends up getting used against worthy targets, we're talking attacks that disrupt entire industries, elections, warfare etc. Do you really think what you'll be hosting will attract that kind of attention and be impossible to take down with simpler methods?
• To survive a DDoS attack you need a lot of resources, from a professional platform (like CloudFlare). The stuff they offer for free is not going to get you through a DDoS. If you'll read their terms you'll see it's worded just ambiguously enough to mean nothing. If you ever actually get targeted by an actual DDoS and you haven't paid a lot of money to a platform like that, everybody will simply drop you instantly (your ISP, your VPS provider, your tunnel provider, your VPN provider etc.) and possibly kick you off their service too.

If the stuff you'll be hosting is static files you can use a CDN service. CDN's are designed to be distributed and redundant so they're somewhat resilient to DoS attacks by default. They'll still kick you off if it gets to be too much but maybe you can weather shorter/moderate attacks.

If you're hosting a dynamic/interactive service forget about it.

What's your budget?

I'd set-up a static website on an AWS S3 bucket. Then you can use AWS Cloudfront to distribute access around the planet.

Cost is mostly negligible unless you are serving big files.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

4 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.

[Thread #906 for this sub, first seen 4th Aug 2024, 21:15] [FAQ] [Full list] [Contact] [Source code]

Crowdsec?

If you don’t want to go full Cloudflare you can mitigate DDOS using these kind of technique locally.

https://blog.nginx.org/blog/mitigating-ddos-attacks-with-nginx-and-nginx-plus

Cloudflare will be a lot more effective in case of attack. But I don’t think most people need more than a few mitigation rules. If DDOS really come, there are very few things you could do to mitigate anyway.

why downvote 🤔