Akamai App and API Protector Reviews

The main use case for Akamai App and API Protector is serving as the WAF, Web Application Firewall.

The standout features of Akamai App and API Protector are rooted in it being the Web Application Firewall, where all traffic gets scanned, including the implementation of web firewall rules, and after this phase, traffic proceeds through the BMP, which is Bot Management.

Akamai App and API Protector exceeds expectations in terms of AI capabilities, and it genuinely combines a plethora of advanced features.

The area in which Akamai excels compared to other competitors with a WAF is in threat intelligence, as threats continually evolve, requiring ongoing updates to backend algorithms to effectively capture smart bots, and Akamai's commitment in that regard is backed by an excellent team, while other providers are still catching up.

There are no significant areas for improvement on the WAF side or for Akamai App and API Protector solution; they are comprehensive in their current state.

I would rate Akamai's support for Akamai App and API Protector solution as good, with no complaints and a consistent level of satisfaction.

Positive

The primary way Akamai App and API Protector helps manage evolving cyber threats is by considering the impact on revenue, with businesses evaluating if Akamai is worth the cost based on potential losses from DDoS attacks or bot attacks, leading us to conduct a cost-benefit analysis that affirmed the necessity of having Akamai in place, despite its hefty cost, as the risk of financial issues outweighed that expense.

The effectiveness of Akamai's bot management in reducing unauthorized access is quite good, although it does require a lot of fine-tuning and tweaking, which involves spending ample time with their support teams to tailor the configuration to our applications.

Akamai's intelligent rate limiting is utilized, though the exact details are not entirely clear.

Regarding the CDN, Akamai's rate limiting provides a faster service and quicker response times, and we haven't measured it closely since we haven't received any complaints, indicating satisfactory performance.

Valuable insights gained from the threat intelligence metrics provided by Akamai's solution include a comprehensive understanding of how many bots got through, the number of high-risk bots that scored above 90 and were subsequently blocked, and the tally of bots that were presented with a CAPTCHA, which all depend on how we set it up.

On a scale of 1-10, this solution receives a rating of 7.

We are a B2C company. We do financial payments using apps. All our traffic comes through this system.

As a product, it has good capabilities, including professional support.

However, it's risky for us to rely on AI for real-time traffic management. We use in-house analytics but avoid automatic actions due to their high impact. For example, I live in a developing country. Everyone has different types of phones, apps, and everything else. So, if someone is using a legacy phone, that is still a use case here. 

If AI decides that this is an end-of-life phone or end-of-life Android operating system, it starts blocking that traffic. We may potentially lose millions or probably thousands and hundreds of thousands of hits per second. Everything is all about how well we serve payments because we're into payments.

So, AI is used for analytics but not for real-time decisions.

We can't afford to block traffic based on AI models due to the variety of devices and operating systems our users have.

Features like scalability and uptime are most effective. 

The solution has both Bot Manager and different features to manage threats.

It could have better analytics and reporting visibility in the OEM console.

I have used it for eight to nine years now. This tool changed its name, it's now App and API Protector.

Their edge network is really good. Edge, CDN, and everything helps us manage our workloads.

So scaling with this tool is easy. It can scale down as well. 

There's no need to scale down, but the amount of traffic we have is managed without any issues.

We have TAM support for customizations and rule management. It’s very helpful.

It’s flawless so far, so I’d rate it a ten.

Positive

While it's more expensive than others, the ROI is good for large-scale infrastructure with millions of hits per second. It’s expensive but serves our purpose well.

We’ve tried other CDNs and services. For example, Amazon’s WAF lacks fine-grain traffic control. Other CDNs couldn't handle our traffic volume. We have a large volume of traffic, millions per second.

The price is higher than others. It could be about 80% to 70% more expensive than other tools.

So, it’s not just a slight difference.

For large infrastructures serving millions, it’s highly effective. For smaller startups, different tools might suffice.

Overall, I would rate it a nine out of ten.

We upgraded from Akamai WAF and ION to Akamai App and API Protector. We upgraded to Akamai App and API Protector mainly for Bot Manager because Bot Manager is included in it.

We were getting a lot of bot attacks, and that is why we got Akamai App and API Protector. We implemented it to protect all the sites across the board. We have multiple sites such as The Indian Express, Jansatta, Loksatta, and The Financial Express. We also have regional sites. We are able to protect all the sites with Akamai App and API Protector.

Akamai App and API Protector provides holistic visibility into traffic and attacks. With the help of Bot Manager and the Bot Manager dashboard, I know from which IP I am getting the traffic and whether it is a good bot user agent or a bad bot user agent. I now know how much traffic we are getting from each IP, which IPs are good, and which IPs are bad. We are easily able to block and unblock an IP and user agent with the help of Bot Manager.

Akamai App and API Protector has saved my time, and I am also able to run my site 24/7. That is the main point. My site should run 24/7. So far, I have not faced any downtime. This is Akamai's top-level security product, and by purchasing this product, I assume that all of our sites will be protected from attackers.

Akamai App and API Protector has helped to tailor defenses for our apps and APIs.

We also use Akamai's Adaptive Image Manager. Before Adaptive Image Manager, we were consuming approximately 350 TB in a month, and after we got Adaptive Image Manager, we were able to save approximately 150 TB in a month. That was good for us.

The support that we got from their technical team has been fantastic. I have never experienced this level of support from other CDN providers.

We did a PoC of Akamai and Cloudflare. One area where Akamai can improve is the captcha part. Cloudflare provides a captcha if there are a certain number of threats. For example, I can assign that if there are 10 requests within a second from a single IP, it should send a captcha to the user. The user should fill in the captcha, and only after that, the user should be able to access our website. This captcha feature should be built into Bot Manager. I love this captcha feature of Cloudflare. Other things are good in Akamai. That is why we are using Akamai. Only the captcha part should be implemented.

I have been using Akamai's solutions since 2012. We recently bought Akamai App and API Protector. We started using it in July this year.

It is stable. I have known Akamai products since 2012. We were using Akamai in a product-based company, and now, we are using Akamai in our content-based company. Indian Express is totally a content-based company, and this product is truly suitable in all aspects.

It is scalable. We can serve data to any number of users. We can serve data from 10,000 to 10 million page users. It is always stable.

They have been fantastic. Bilal, Nihal, and other technical team members provided us with great support from the beginning. 

Before Akamai App and API Protector, we were using Akamai WAF and ION. We were getting a lot of bot attacks. We had multiple rounds of conversation with Akamai. They gave us a PoC of Bot Manager. At the time of PoC, we are able to secure our sites. After a long discussion with the complete team, we finally got Akamai App and API Protector.

I was a part of the deployment process of Akamai WAF and ION, and I handled the complete deployment when we deployed Bot Manager. When we are using something new, the process is definitely difficult, but after understanding the process and having meetings with their technical team, it was easy for us.

The Akamai support team helped us at every step, we upgraded from Akamai WAF and ION to Akamai App and API Protector very smoothly. 

I have been using Akamai since 2012. It is the finest product in terms of Content Delivery Network (CDN). I always recommend using Akamai in place of other products. We did a PoC of Cloudflare and other solutions many times, but we found Akamai to be the best.

I would rate Akamai App and API Protector a 9 out of 10. The main reason for switching to Akamai App and API Protector was Bot Manager, and Bot Manager is working properly now. I am happy with Bot Manager. My sites are now protected. In terms of cache, Akamai is able to cache my data in a proper manner and serve it in a proper manner. They provide us with what we require.

With Akamai App and API Protector, we can define all our APIs, and we can use the solution for different purposes. It is the way we use API gateways like Kong. We can define our keys here, and we can define a limit at which we can start throttling traffic.

With BMP, we can protect our transaction endpoints from advanced and sophisticated bots.

URL protection can help us from DDOS attacks.

All the solution's features are very good. Security-wise, BMP has helped us a lot. Hopefully, the account protector will also be good.

In regards to protection from bots, Bot Manager Premier (BMP) has helped us a lot in protecting our transactional endpoints.

We are experimenting with EdgeWorkers to write our own code at the Edge level. That is something that came last year. Not a con but we could grow to be much better.

Additionally, it needs to keep on evolving with the latest bot trends. Nowadays bots are evolving daily and Akamai has to come up with a solution that is able to keep up with the pace of these evolving bots.

We have been using API gateways and API throttling for a couple of years. They are good features, however, we do not use them extensively. 

URL protection is a beta feature that is a little similar to API throttling and we have started experimenting with it.

We have been using BPM for the last three to four years. It is one of our best products till now but as bots are getting advanced, this feature needs to evolve a little.

Bot Manager Standard help us to protect ourselves from less sophisticated bots like browser impersonator or search engine impersonator bots.We have been using this for around 4 years.

We have been using WAF protection for around 5 years. It provides us protection from web application attacks.

The account protector has helped to detect fraud and to protect our login endpoints. We are still experimenting with it.

The solution is stable. Akamai gives us a 100% SLA, but issues sometimes happens about once a year.

There are more than 1,500 domains protected on the WAF, and it's quite scalable.

Our experience with customer support is good.

Positive

I did not previously use a different solution. I had demos with other companies/vendors but not hands-on knowledge. 

We you have some technical knowledge related to the CDN field then I would say it's quite simple.

We can set up the solution ourselves. We have around 80% of the access. But in case we are stuck anywhere or we want some advanced setup to be done, then Akamai helps us. We just have to raise a ticket or email them, and they help us.

We are using Akamai's bundled service so all the features and solutions are included in Akamai's bundled cost. One reason not all people use Akamai is that it is a little bit more expensive than some other providers so you have to see your use cases before choosing Akamai.

We evaluate other options every few years but for now, Akamai suits us best based on our use cases.

You should use the solution. Since it is expensive, however, you also have to weigh the type of traffic your website has. Based on that, you have to weigh whether you want to spend that money or want exactly that type of protection. I rate Akamai App and API Protector a nine out of ten.

We are using Akamai App and API Protector for security purposes. We were not able to do monitoring of each and every API. It was really difficult. Most APIs are public, so we were looking for a solid security solution. Akamai gave us a demo. We liked it and purchased it.

We started using Akamai App and API Protector very recently, but we have been using Akamai WAF as well as Akamai CDN. We were using another cloud distribution solution for content delivery, and we were facing some latencies and issues with the delivery. We then moved on to Akamai CDN. It was very fast, and it reduced the latency a lot.

The benefit of using multiple Akamai solutions is that we have a single vendor, which makes the management and interaction very easy. Getting help for different parts becomes a concern when you are using multiple vendors. For each and every part, you have to call a different vendor, whereas with a single vendor, if you are getting multiple problems, you have to call once, and all the problems will be solved.

It provides holistic visibility into traffic and attacks. We can see the logs. We can see what it is blocking and which attacks are coming. It already takes care of them. I am able to make my applications secure with Akamai.

Akamai App and API Protector saves time. The Akamai GUI is very user-friendly. Every detail is visible. Whatever you want to change, you just change it, and the best part is that whatever change you are doing, it is going to the stage first. There is zero downtime for configuration changes.

Our apps and APIs are protected from new and emerging threats. Akamai already takes care of all the attacks that have already happened or are happening. They maintain their own database. They are updating their threats database, and they are providing the remediation of those attacks. By using Akamai, I am not at all worried. I know if a new attack is there, the Akamai team would already be working on that. They will provide a solution before it attacks us. 

Akamai App and API Protector helps to tailor defenses for our apps and APIs. Our developers can work on and develop APIs without any worry of getting those hacked. Akamai is always there as a savior.

The most valuable feature is that we are getting security for each and every API.

I do not see any area for improvement. Akamai is already maintaining its own databases for the security concerns, vulnerabilities, and attacks that are there. If anything, they should have a solution in the infrastructure security area as well. They should not be only in cloud cybersecurity; they should also be in infrastructure security.

We have been using Akamai App and API Protector for two or three months. We recently purchased it.

Akamai is already a leader, so there is no question about its stability. It is already stable.

It is highly scalable. Akamai as a company is using emerging technologies, so it is definitely scalable.

Their support is prompt. We get the chat or call support instantly. If there is any problem that was not addressed before, we get prompt support for that. 

The deployment process is nice. There is zero downtime. Without impacting your production. we can deploy onto the network and analyze it. You can see how it is helping you. Once you approve it, only then it goes to production.

If you want quality, you have to pay the price. Its price is fair. Their account managers are also very helpful. They help you a lot with pricing even though they are working with Akamai.

I have used Akamai WAF. It is very good. It is very user-friendly, and all the configurations are easy. You can do that in minutes. I have also used Akamai CDN. We were using a cloud CDN, but because of latency, we moved to Akamai CDN. We did a PoC, and the latency reduced drastically, so we moved to that.

Overall, I would rate Akamai App and API Protector a 10 out of 10.

The majority of our traffic is app-based. We are a mobile-focused company. We have a news aggregation platform, and we have a TikTok type of social media platform in India. It is one of the largest platforms. Everything is on mobile applications, so we have a heavy use of APIs. We use Akamai App and API Protector to look at the traffic patterns and identify malicious traffic. There are people who try to inject malicious data and get into our infrastructure, we also use it for that. These are two use cases for which we use Akamai App and API Protector.

With Akamai App and API Protector, we mainly wanted to implement security on the edge rather than bringing it on-premises. We have more than 300 million users. We have quite distributed traffic. We cannot bring all the traffic in and do the slice and dice to identify threat factors. We just want to address it at the edge, which helps us to get clean traffic. That was a major reason. Because it is a publishing and UGC environment, a lot of bot activities are there. They want to get content from our sites and put it somewhere else. They want to make traffic out of it. To identify that, our resources were getting burned, and we just wanted to protect them from that. That was one key reason for implementing Akamai App and API Protector.

By implementing Akamai App and API Protector, we could address these challenges. We were able to filter out quite a lot of bot traffic or the traffic run by scripts. On the WAF side, we have seen a lot of accesses and command line injections happening on the system. We were able to isolate those as well.

With Akamai App and API Protector, we have attack traffic visibility. It does whatever we define as a baseline. Anything that reaches the baseline is called an attack. That is how the system understands an attack. They have ASG that gives automatic recommendations to reduce false positives, but in some use cases, it is still tricky. When we have highly variable traffic, we have to keep improving or altering our configurations according to the traffic pattern that we are anticipating. It is a manual effort that has to be done because only we know when the traffic is going to surge. For example, when there is a cricket match, we know that the traffic is going to surge, so we may need to slightly adjust certain parameters to adapt to that. Otherwise, that traffic will be identified as malicious traffic and get denied. 

Akamai App and API Protector is able to do the cleaning of the traffic so that it reaches the origin. Generally, we are prepared for higher capacity because we do not know when an event can occur and there could be a surge in traffic. Akamai App and API Protector has helped us to clean the traffic to reach the original pages, which is necessary.

To protect our apps and APIs from new and emerging threats, their support team consistently reaches out to us. Whenever a new CVE is there, they implement the patches directly into the portal. The good part with Akamai is that we have an option to review a patch, and if we want, we can apply it. Many solutions in the market are already patched at the backend, so there is no question of monitoring whether that patch is required or not, whereas with Akamai, whenever they apply a CVE, I have the option to review whether it is required or not, and because of that CVE, whether I have some issues with my current traffic pattern. There can be a false positive and the traffic might be getting denied. I can then look into that. 

Traffic filtering and WAF are valuable. We have to have something on the edge for protection. The majority of our traffic is routed via Akamai. So, it adds value to our security.

I have given them a couple of suggestions through email. 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.

Another request was to be able to segregate traffic for different app versions. A few of the APIs are already out in the market and are built into the applications. We cannot go and change those applications. Those applications are still being consumed, so we need a different strategy for those applications, whereas modern new applications are built using a different design. We have quite a lot of versions deployed since 2008, so designs are very different, and applying the rate limit for each API has its own challenges.

Its pricing can be slightly better.

From a security solution standpoint, we have been using it for three years.

Its stability is amazing.

It is quite good. We tested it, and we have seen the scale that it can handle.

They address the queries in a timely manner. They do not delay it, but in security, there could be a slight slowness in terms of assessing what can go wrong while trying to fix a problem. This can slow down certain processes. Sometimes when an attack happens, we need to act immediately on it, but blocking something just by looking at the pattern is not always the right thing. It might be the right thing for an immediate fix, but if you look at the damage it can cause, it can get complicated.

It was not challenging. It was smooth. I did not find it very complicated. We also have a self-service model on Akamai. That was also not challenging. Their security portfolio is still evolving. Certain features and certain documentation have to be more detailed, but we did not face too many challenges while doing the basic things.

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.

We did a couple of PoCs. We went for Akamai App and API Protector because the majority of traffic is driven through Akamai. Their support is good. The product is meeting the need.

In terms of comparison, from a solution standpoint, there are different modules and different offerings. The industry is moving at the same pace from a solution standpoint. The differentiation comes in terms of how the service is provided and what scale it can support as a security solution. It is not only about features.

We also use Linode, but it does not interact with Akamai App and API Protector. It is an independent deployment.

I would rate Akamai App and API Protector an eight out of ten considering the pricing and multiple products available in this sector. It meets my needs, and I would recommend it to others.

We are using Akamai App and API Protector for the protection of our APIs. We have an OTT platform that serves as an aggregator of multiple providers. There are multiple channels streaming on the OTT platform. We need to protect the APIs as well as subscriber information and general information. Akamai App and API Protector protect us from hackers and malware attacks. It protects us from malware IPs and helps with proper streaming.

Akamai App and API Protector has improved the experience for our users. When our users are streaming IPL or some other event on our platform, if there is buffering going on or users are not able to log in to the portal or the website, they have a bad experience. Akamai App and API Protector helps to provide a better experience to our customers.

Akamai App and API Protector also provides protection from bots. We have enabled bot protection.

Akamai App and API Protector provides holistic visibility into traffic and attacks. We are receiving monthly reports of the kind of attacks that are coming, how they are protecting, and what kind of remediation they have done. We are receiving monthly reports.

Akamai App and API Protector has definitely saved us time. It provides protection at the gateway level. It frees up our time, and we can sleep easily at night knowing that Akamai App and API Protector is there.

Adaptive stream delivery and WAF protection are valuable.

A lot of piracy happens in India and other countries. If there is a product for protection from piracy, it would be great. For example, there are multiple hackers that hack your event, and there are some channels that pirate and publish the event on some other website. We protect our streaming through DRM and different technologies. We are also protecting the website, but hacking is still happening. If they can work on protecting from piracy, it would be great.

I have been using Akamai App and API Protector for the last three years.

It is scalable. When we have big events happening in India such as IPL, G20, or elections, we need to scale up the channels because we get a lot more traffic. We have never faced any issues. From the customers' perspective, we are receiving very good feedback. There is no buffering or other issues with streaming.

Their technical support is very good. When we have big events coming up, such as a cricket match or a G20 event, we can open a ticket in advance requesting immediate support during the event. If something happens, we immediately get support, and an engineer gets assigned. We get a dedicated resource. That has been very helpful.

We have used the AWS platform for the protection of WAF and other things. We have used their WAF protection product. 

It was a very easy process because they assigned a dedicated resource. They communicated well about how much time they would take and what steps they needed to follow. We could easily implement this product. 

We have assessed other products as well. We have been using Akamai CDN, and they gave us a demo of Akamai App and API Protector. We did a PoC, and during the PoC, we could see the protection that it provides. We could see the attacks that were coming and how Akamai App and API Protector was able to protect. There is a passthrough method in Akamai. They gave us some reports that we could analyze to see its benefits. After that, we implemented it. Akamai was also at the number one position in Gartner and other reports.

I would rate Akamai App and API Protector a 10 out of 10.

The tool protects organizations from attacks, SQL injection, and DDoS attacks. We mostly used it for DDoS attacks.

The solution clearly shows us what is happening in the background in real-time. All the rules we implement work exactly as expected. The product is user-friendly.

All the features in the product are very good. The IP/Geo Firewall can block access based on the geographic location of the IPs. The product has WAF and custom rules. The tool provides DDoS protection and IP reputation. It is a good package. I recommend all the features to others.

The custom rules must be improved. If we have a domain to be monitored, we can use the solution to alert us if a certain specification is met. If we need only 20,000 transactions, but there are 40,000 transactions, the product alerts us about it. We don't have the option to block it. The tool must provide the users with such options.

I used the solution three months ago.

I have not faced any issues with the tool’s stability.

The tool is scalable. Around 400 people use the solution in our organization.

The technical support team has to improve on its availability.

The product is cloud-based. The deployment process is very easy. Once the domain is integrated, the solution automatically protects against DDoS. The deployment takes only a few hours. It’s a pretty simple integration. It protects all the domains automatically, irrespective of specific paths. For example, facebook.com/login will be protected automatically. We need not integrate it manually.

Akamai has its own staging environment. To implement a change, we add it to the staging environment and ask the relevant team to test it. If it’s okay, we enable it in production. It is a good feature. I do not see this feature in other products.

The product is expensive, but it is worth the money.

A person unfamiliar with Akamai can learn to operate and check the product in 30 minutes. It’s a user-friendly tool. People must keep a check on the cost of the product because the cost is based on the data usage. Overall, I rate the tool a ten out of ten.

We are a media company, and the news delivery has to be the fastest. Any live event, such as a cricket match or election results, has to be really fast. We cannot afford any downtime or any factor like that. We need immediate delivery. There are things like caching, so when we have a five-minute TTL, we have to reduce it or increase it immediately. Those are mostly the use cases we have. We use 301, 4xx, and 5xx redirections a lot. That is pretty much the day-to-day activity. The image optimizer and things like that also come in handy.

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. There was a security issue recently, and Akamai helped us with that. They gave us the IPs that were accessing our page, that were not able to get the correct page, and that were not from our region.

It has not saved us time because it is a time-consuming process. Once we get stuck with something, we have to explore and try various versions in staging and production, so time is something we need to have in our hands.

The WAF functionality is also there with Akamai. Our security staff takes care of that. I do not manage that. We get the IP addresses from Akamai support, and then our cybersecurity team evaluates them. It helps with that. We have also implemented rate limiting, which is helpful when there are bot attacks. It handles that as well. 

The whole product is valuable. I cannot distribute it and choose one feature. It is very handy. It was easy to learn as well because I was a fresher, and I did not have much knowledge about DevOps, but within two to three weeks, I could learn what it is. It was easy.

There are some challenges. I have been interacting with their support about an issue. 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.

I have been in DevOps for a year. I am a fresher, and I have worked with Akamai for six or seven months. In our organization, I handle the redirection and the Akamai part. 

It is stable. There have not been many errors over the past year. 

It is scalable, but it is not an area that I work with.

We simultaneously use other solutions for different products we have, but I personally prefer Akamai, and I voted for it as well. Other vendors are more focused on money. They want more money from us instead of giving us more ease, whereas with Akamai, we get to use what we need on a daily basis. There are only some areas for which they want more money, such as for advanced rules, but the other vendors in the market are majorly focused on making money rather than finding solutions.

There are multiple products, and I was involved in some of them. We use various domains. This company is way back from the times of Mahatma Gandhi, but then the digital part came, and we are setting up and making more domains. I am a part of that. 

The setup process is pretty easy. With the proper guidance of my mentor, I am able to do that pretty easily.

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. 

Overall, I would rate this solution an eight out of ten.

I have been using Akamai's Content Delivery Network and WAF products. The Akamai App and API Protector product is new to us. We are still implementing it. 

We were facing some security issues. We faced some attacks in the past. That was the reason for implementing Akamai App and API Protector. We wanted to protect our website. That was the main reason.

The WAF features are valuable to us. When I see the WAF features, there are a lot of categories and subcategories. You can see what attacks are happening on the system. The dashboard is the most interesting feature of the Akamai portal where you can have a detailed analysis of all the attacks that are happening. You can drill down an issue and see exactly what is happening, who are the bad guys attacking your website, and how Akamai is protecting the website. That is the most valuable feature.

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.

We have recently onboarded Akamai App and API Protector.

Akamai as a SaaS product is very stable. I have not seen any downtime. 

We did not use any solution similar to Akamai App and API Protector, but we did use Akamai WAF.

The Akamai Tech team had a very professional approach. They analyzed the entire system. They saw all the logs, and they came up with their presentation and slides listing the areas that were there. They advised us on the areas where we needed to focus and the attacks that were happening. They highlighted all those areas. They built the configuration for us and asked us to review that configuration. After reviewing, they asked to implement it on staging and then make it live. It was a very professional approach that I saw from the Akamai tech team.

When you implement it, it is very smooth. The UI is very familiar. You can easily see all the components and features. They provide guidelines. There are forums where you can find a solution. All the help is there on the website to implement all the components.

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

We looked in the market and checked all the vendors that could provide this facility. We found that Akamai is on top. We reached out to Akamai and started using it.

When it comes to Akamai products, I have seen their three products. Akamai Security is one. Akamai Content Delivery Network is another one, and then there is also Akamai Cloud. We use two of them. We are not using Akamai Cloud. In terms of integration, WAF with Content Delivery Network works very well, but I do not have any idea about other products.

Overall, I would rate Akamai App and API Protector an eight out of ten.