Although it may look like AbyssGuard and CloudFlare offer similar tools, they are quite different. CloudFlare protects mainly your server while AbyssGuard focuses on your website. Using the one does not exclude the other one providing you need the services offered.

Whit AbyssGuard you can fine tune every single thread recorded to your logs, see the IP address, the page opened and find behavior patterns. All the stuff that you probably won't find in any other tool.

As said above, you can use both AbyssGuard and CloudFlare with a little fine tunning. While using CloudFlare their service will take up the IP address used by the visitor and pass it by as another server variable. You need to follow one of these guides in order to make your web server recognize which IP address is the real one, in order for AbyssGuard to work correctly.

Why don't we implement this directly into AbyssGuard? It's easy enough to look for CloudFlare headers and take the right IP address, the problem is that someone may fake it providing inifite resource of IP addresses to fool AbyssGuard. Internal check would need to be in place to validate if the CloudFlare source is legitimate. This from one side will take up resources from your server and slow down your page loading; and from another side in order for the list to be always accurate and up to date it will depend on us updating the list and from you updating the Client. Too many places where the things may go wrong, so instead the best way to use both is to simply configure your web server to pass the correct parameters to your website.