Quality Edge Delivery Service
December 09, 2021

Quality Edge Delivery Service

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Fastly Deliver@Edge

We used Fastly both as the pre-configured caching backbone for all our customers as well as a highly-customized edge provider for customers who required more control than the pre-configured version gave them. The use cases could be anything from SEO optimization to enhanced security protection. We also implemented Fastly as a means of providing additional functionality, such as edge logging and image optimization, that could be scaled across multiple web properties with a single configuration.
  • Comprehensive API.
  • Feature-rich UI.
  • Excellent documentation.
  • Fine-grained custom VCL.
  • WAF is hard to configure.
  • No comprehensive rate limiting without a pricey upgrade.
  • Account access controls are extremely limited.
  • Support.
  • Security - either the in-house waf or recent Signal Sciences acquisition.
  • Speed.
  • API-driven allows us to use Terraform or custom REST calls to quickly spin up new configurations.
  • Adding a custom fastly implementation to our sales SKUs opened up 10s of millions of dollars in ARR in a single year.
  • Fastly enabled us to sell to nearly 100 customers a year that we otherwise would not have been able to service.
  • We did end up needing to spend nearly $500k/yr for custom TLS certificates (2000 domains).

Do you think Fastly Edge Cloud Platform delivers good value for the price?


Are you happy with Fastly Edge Cloud Platform's feature set?


Did Fastly Edge Cloud Platform live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Fastly Edge Cloud Platform go as expected?


Would you buy Fastly Edge Cloud Platform again?


The service is really well-suited for pretty much any site that is primarily display-driven (that is, mostly GET requests). The network is able to handle massive volumes of traffic and their POPs have spread out pretty much anywhere that it's easy to get them (so basically everywhere but China and Russia). My team witnessed several large-scale attack attempts on some high-profile websites (attacks in the 10s of millions of requests per second) that were mitigated before ever coming back to the actual application; in one case we didn't realize the attack had happened until we looked at the logs the next day. Because it's a cache store option, the default configuration does not cache POST responses, and it can be difficult to set up things like authenticated paywalls as a result.