So your product isn't a WAF that is routed to using the DNS, it is a "firewall" that lives on the server? I am assuming it is looking at the incoming logs. If so how much memory and CPU does the application take?

Or do you hi-jack the server traffic, route it through your servers, then route back to the server? If you do it this way, how, do you do this without affecting the application.

Does this work on Ngnix and Apache?

Dear Sumo-ling,

Indeed, we developed our product for users of all levels, so you don't have to be tech savvy to benefit from it. Our main goal, from the very beginning, was to help small businesses to protect themselves in the Internet. Therefore, there is no need to dig into the DNS settings or server settings.

All the traffic is scanned on the client's side. To our best knowledge, CPU and memory usage increases up to 20-30%.

We offer PHP WAF that is supported by all web-servers, including NGINX.

Hope it helps!

Best,
Tatiana