Akamai App and API Protector vs StackPath WAF comparison

"They have a fantastic tool for analyzing and viewing your traffic."

"The product is user-friendly."

"We are getting security for each and every API."

"I can attest to its benefits in terms of understanding and mitigating threats...The solution's technical support team seems to be pretty responsive."

"The CDN and the WAF features are the best."

"I have contacted the support team of Akamai... I am happy with their responses and answers to my problems."

"It gives us a report of traffic. It gives us a report of the day-to-day URL traffic, and it also gives an individual report. If we reach out to Akamai, they give us the IPs as well."

"Features like scalability and uptime are most effective."

"The product’s most valuable is WAF. The authentication feature helps us protect WordPress sites."

"There are some issues with pushing configurations across a network. It still takes about 20 minutes and that means to retract it's another 20 minutes."

"The product should provide a secure NTP."

"The interface is a little bit clunky and can be improved."

"Could integrate more features for each security."

"One thing I asked them is to integrate the API discovery product that they have and push that data into Akamai App and API Protector so that we do not have two types of reviews to identify the type of traffic. We already know the APIs that are frequently getting used, so analysis becomes easier. We can integrate both products and use them."

"Support and the pricing need to improve."

"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."

"The product’s performance for caching feature needs improvement."

"Its price is at the medium level. It is not very high. It is also not very low. It serves the purpose."

"The price they are offering is quite reasonable for premium customers, but it's very expensive if you're a small and medium-sized enterprises."

"Cost depends on the volume of traffic."

"There is no license at all for Akamai. They are going to charge us only for the usage."

"Its price is slightly high. Every company has a justification for the high price. Overall, it feels worth the money based on how the service has been structured, but we do negotiate it."

"One reason not all people use Akamai is that it is a little bit more expensive than some other providers."

"Based on the billing discussions in the DevOps team, Akamai's cost does not seem to be a major thing. However, LOE is an issue. When it comes to support, we know that even all the competitors do this. For a 30-minute issue, they give us a LOE of one or two hours. That is a basic practice, but that is something we worry about."

"The solution is expensive."

"The product is affordable."