What is our primary use case?
We use Akamai Kona Site Defender because we need CDN. We have mobile apps, and we host them internally. Sometimes, we also deploy an IPA file for iPad. I think all the users from our distributor are going to download directly from our server. We use Akamai to distribute all the IPA files to our network provider without any significant latency for our distributor.
What is most valuable?
I like that the charges are all based on usage and labor costs. For the time that we spend onboarding almost 252020 FQDN, Akamai charges us only for the traffic usage, but it's only charging us for the labor costs for onboarding.
What needs improvement?
It would be better if there weren't any issues with latency. We had latency issues, but I think they are all solved now.
What do I think about the stability of the solution?
Akamai Kona Site Defender has been stable so far.
How are customer service and technical support?
Because our third-party partner has a good relationship with Akamai, I think they can call the Akamai to join the incident call when an incident is happening. I think they're quite good and responsive for that. There is also a lot of documentation online regarding troubleshooting.
How was the initial setup?
The initial setup is quite easy because we mainly outsource it to another company.
What about the implementation team?
We just ask the third-party provider to implement the solution or engage Akamai and make some changes.
What's my experience with pricing, setup cost, and licensing?
There is no license at all for Akamai. They are going to charge us only for the usage.
What other advice do I have?
I would recommend this solution to potential users. I think if the FIC has a CDN, it's easier in terms of onboarding. In terms of the commercial part and charging, I think Akamai is more efficient. I think it's important to have a CDN feature inside.
On a scale from one to ten, I would give Akamai Kona Site Defender a nine.