We performed a comparison between Akamai App and API Protector and Imperva DDoS based on real PeerSpot user reviews.
Find out in this report how the two Distributed Denial of Service (DDOS) Protection solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It is scalable for DDoS."
"The support that we got from their technical team has been fantastic. I have never experienced this level of support from other CDN providers."
"The solution can scale extremely well."
"The features are powerful and better than F5."
"They have a fantastic tool for analyzing and viewing your traffic."
"The product has a good user interface."
"The most valuable feature is the custom rules feature. This is because many of our customers require a lot of custom rules. Because it's a very customized project for our customers, I think they have the best of everything already."
"The most valuable feature is the DDoS protection, which is the main reason we got it."
"The most valuable features for us are the DDoS and Bot."
"Provides Anti-DDoS protection, as well as other protections like SQL injection, Cross-Site Scripting, and antiscanner. These types of protection are valuable to the business due to the daily attacks on our portals, and that often cannot be seen without a tool like this."
"I like the user-friendly interface."
"The technical support is excellent."
"The most valuable features are DDoS protection."
"It's very pretty easy to onboard the URL."
"It blocks all types of attacks."
"Integration with IBM AS/400 and Db2 is okay."
"Customer support has room for improvement."
"In terms of precedence of Akamai rules, the last one is implemented. That is the one that is operational. If two rules contradict, the last one is implemented. We had a clash, but it was really tough to find that out. I would like to have a rulebook because, in their architecture documentation, it is not mentioned anywhere that if two rules clash, the last one works, and if it does not work, then what to do. This is something we were debating today with their tech support. With AWS, we get documents for the issues so that they do not occur in the future. Akamai's support and knowledge base needs to be improved."
"Akamai App and API Protector is very new to me, so I do not have any insights on improvement areas for the product. However, when we ask for some help, it can take some time. We understand that the job is done by professionals, but if that time can be reduced, it would be great."
"It would be nice if Akamai Web Application Protector's price is lowered and made cheaper."
"The interface is a little bit clunky and can be improved."
"The custom rules must be improved."
"It's fine for a simple tool, but as I recall, if you encounter a lot of bots, scrapers, and other things, you'll need this tool bot and this other thing they offer called Bot Manager."
"The solution could offer even more integrations."
"We would like them to hire people in Sweden because it's quite hard when people are sitting in the UK or Belgium because some of the customers really want them to be local."
"Users would benefit from better documentation. There is official documentation, but sometimes we need more detail. We have some use cases that are not so run of the mill. It would be great if there was a knowledge base that we could go to for more answers."
"The solution should integrate with something that looks at continuous security management."
"I would like to see automated reporting to improve visibility."
"The weakest point of Imperva is their first level of support, which should be improved. They should also improve the access and security logs viewing directly on the portal. I would like to see better access and security logs through the portal and not only through a SIM solution. Currently, if you want to explore your access and security logs from Imperva, you need a SIM tool or a SIM infrastructure on your side to do it. You can't do it manually or directly through the portal, which is a big problem for us. I had a call yesterday with Imperva for the roadmap, and I just told them this. They agreed that this is an improvement point from their side."
"Its price could be improved. It is quite expensive. It will be good if we could export the configuration. Currently, to control the configuration, we need to go to each website, which is not very convenient."
"Some maintenance must be performed by our IT team."
"We had an issue when securing the web applications for DDoS protection."
Akamai App and API Protector is ranked 3rd in Distributed Denial of Service (DDOS) Protection with 27 reviews while Imperva DDoS is ranked 7th in Distributed Denial of Service (DDOS) Protection with 74 reviews. Akamai App and API Protector is rated 8.4, while Imperva DDoS is rated 8.8. The top reviewer of Akamai App and API Protector writes "Easy to learn and gives us a report of traffic". On the other hand, the top reviewer of Imperva DDoS writes "I like the content monitoring feature which I haven't seen in other WAF solutions". Akamai App and API Protector is most compared with Cloudflare Web Application Firewall, Microsoft Azure Application Gateway, AWS WAF, Prolexic and Prisma Cloud by Palo Alto Networks, whereas Imperva DDoS is most compared with Cloudflare, Akamai, Arbor DDoS, Radware DefensePro and Fortinet FortiADC. See our Akamai App and API Protector vs. Imperva DDoS report.
See our list of best Distributed Denial of Service (DDOS) Protection vendors and best Web Application Firewall (WAF) vendors.
We monitor all Distributed Denial of Service (DDOS) Protection reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.