Can't do better than StackPath if you need just a CDN
August 26, 2021

Can't do better than StackPath if you need just a CDN

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

Overall Satisfaction with StackPath (formerly Highwinds) CDN

We're a publishing company, so the entire company benefits from our StackPath deployment in terms of site performance. StackPath has data center locations in major US cities, placing our content (images, logos, JS) quite close to our user base. It has helped greatly in maintaining uptime performance; we've never, ever had an issue with StackPath's CDN and Edge services not being available in the 3+ years we've used them.
  • Service availability
  • Ease of integration with various web properties
  • Easy to use administration interface
  • Free private SSL certs for CDN
  • Cheap object storage and delivery
  • The management interface is easy to use but a bit crowded. Wouldn't mind being able to create a custom dashboard.
  • The web application firewall could be more robust when compared to Cloudflare.
  • They don't yet support TLS1.3
  • They will serve assets when your origin is not available but it isn't a full site delivery service.
  • CDN and multiple POPs
  • Competitive pricing
  • Performance and availability
  • Easy 25-30% improvement in website performance vs non CDN solution
  • Less expensive and faster object storage than AWS
  • Aided greatly in maintaining KPIs in terms of performance, availability
Better CDN pricing than Amazon CloudFront and Fastly. We knew Akamai was expensive but it is the best when it comes to content and application delivery. For CDN and Object Storage, it is easier to setup and manage than AWS. Fastly offers different services than StackPath and their CDN bandwidth charges were nearly 60% higher than StackPath when we first signed up - that may have changed since we first signed up however.

Do you think StackPath Edge Delivery delivers good value for the price?


Are you happy with StackPath Edge Delivery's feature set?


Did StackPath Edge Delivery live up to sales and marketing promises?


Did implementation of StackPath Edge Delivery go as expected?


Would you buy StackPath Edge Delivery again?


Well suited to:
  1. Startups - Very competitive pricing, better than AWS for object storage and CDN.
  2. The less technical - for those looking to implement a CDN, it doesn't get any easier than StackPath
  3. The more technical - Well documented API, serverless scripting and container deployments
  4. Fast object delivery - StackPath tends to be faster (sometimes much more ) than AWS S3. See below however...
Not so well suited to:
  1. Multi-tiered web applications
  2. Ultra high bandwidth requirements. Stackpath isn't meant to be a substitute for AWS or Azure when you're looking to push 100s of TBs of traffic.
  3. Object storage works well if you don't need fine-grained bucket lifecycle or permissions management.

Evaluating StackPath and Competitors

Yes - We had been using MaxCDN which was purchased/absorbed by StackPath. MaxCDN was OK but we find StackPath to be much better. Prior to that, all assets were served from webservers. Our ISP included a healthy amount of bandwidth (30TB or so) but you can imagine how poor performance was; they also had their own CDN but lacked enough POPs as to be useful.