Skip to content

Gcore versus CacheFly

Easily compare Gcore and CacheFly for POP locations, products, pricing, features & support. We hope this helps you better understand the similarities and differences between these content delivery networks.

Gcore logo CacheFly logo

Company

Company Gcore CacheFly
Short profile Gcore is a global CDN with a focus on gaming: "We expand the geographical presence of your game and speed up downloads for your players". Gcore is headquartered in Luxembourg and employs 400+ people. Launched in 2002, CacheFly developed the world's first TCP-anycast based content delivery network. CacheFly has a focus on optimizing the CDN for throughput and has steadily built out the network to now have 50+ POPs on 6 continents. CacheFly provides a 100% uptime SLA and takes pride in acting as 'consultants to our customers'.

Products

  • Yes = Yes
  • Sortof/partially = Sort of/partially
  • No = No
  • Unknown = Unknown
Product Gcore CacheFly
Dynamic content deliveryNon-cacheable content delivery. User login, shopping cart ... Yes Yes
Small file deliveryStatic object delivery; caching of small files (file size <1 MB) Yes Yes
Large file deliveryStatic object delivery; caching of large files (file size >1 MB) Yes Yes
Live videoDelivery of live video. RTMP? Transcoding/transmuxing? Yes Live Streaming Yes Ultra Low Latency Video Streaming
Video on demandDelivery of on demand video Yes VoD Yes VoD
Image OptimizationAutomatic image transformation/compression/optimization Sortof/partially Yes Smart Image Optimization
DNSAuthoritative DNS for customer domain Yes DNS No
WAFWeb Application Firewall Yes WAF Unknown
Anti-DDoSDDoS attack protection. Specific product(s) for this. Yes DDoS Protection Unknown
Private CDNDedicated edge resources & custom configs No Yes Fully custom solution
Edge ComputeRun your code on CDN edge servers No Sortof/partially Custom solutions available for edge scripting

Network

Region Gcore CacheFly
North America 15 17
Latin America 10 11
Europe 17 14
Russia & CIS 36 2
Asia excl. China 13 7
China 0 2
Oceania 2 3
Middle-East 10 5
Africa 3 1

Pricing

Pricing & contract duration Gcore CacheFly
Minimum contract term None 1 month
Minimum monthly costs $25 $595 (35 TB/m)
Requests costsCustomers pay for client to CDN requests First 1 billion free, more cost $0.0075/million No
Ingress costsCustomers pay for origin-to-CDN bytes transferred Yes Yes
NA/EU traffic (low volume) $0.025 per GB n/a
APAC traffic (low volume) $0.025 per GB n/a
LATAM traffic (low volume) $0.025 per GB n/a

Features

  • Yes = Yes
  • Sortof/partially = Sort of/partially
  • No = No
  • Extra costs = Extra costs
  • Unknown = Unknown
Web acceleration Gcore CacheFly
Instant setupSign up, configure, start testing. Yes No
Change propagation delayHow fast do config changes propagate to all POPs? Yes ~15 minutes Sortof/partially 5 - 180s depending on the change
Apex/root domain OK Blog: Root domain on CDN and performanceNo performance degradation when using http(s)://domain.com Sortof/partially Custom solution (host your DNS zone ...) Extra costs Must purchase dedicated IP
tooltip Or use DNS provider that can do CNAME flattening
HTTP/2 Yes Yes
IPv6Do the edge servers have IPv6? Yes No
Compression CDN Guide: CompressionReduce file size for faster delivery Yes Resend from origin, or compress on edge Yes Resend from origin, or compress on edge
Origin pull - protocolHTTP only or HTTPS possible too? Yes HTTP and HTTPS Yes HTTP and HTTPS
tooltip Match client to edge request protocol is possible
Origin pull - Host headerUse client > edge value? Set specific value? Yes Can be different from origin host Yes Set specific Host header value or forward value from client to edge request
Origin ShieldOne POP pulls from origin, other POPs pull from the shield POP Extra costs Yes
Push / uploadStore your content directly on CDN, no customer origin Unknown Extra costs FTP. Some storage free, more storage available at additional costs
Cache control - CDN caching Yes Origin or CDN controlled Yes Origin headers are honored. Can config overrides
Cache control - client caching Yes Origin or CDN controlled Yes Origin headers are forwarded to client. Can config overrides
Serve Stale CDN Guide: Serve StaleCDN serves cached but expired content in case origin is in trouble Yes Always Online Yes CacheFly support team can activate this edge behaviour
Purge CDN Guide: PurgeInvalidate or delete cached objects on CDN Sortof/partially Purge Speed Yes Purge Speed
Purge - capabilities Yes Purge all, directory, and by file type/pattern Sortof/partially Purge all and by directory, not by tag or header
Analytics Yes Many metrics, real-time updates Yes Near real-time, lots of metrics
Log files Extra costs Export logs to your storage. Logs are exported at the end of each hour. Extra costs Pull via FTP or have pushed to customer endpoint
tooltip Logs are 5 minutes delayed
API Yes Purge, analytics, configuration Yes Purge, analytics, configuration
HTTPS & Content Protection Gcore CacheFly
CDN domain HTTPSUse the CDN's domain, like cloudfront.net Yes Yes Free
Customer domain HTTPSYour domain in the CDN's certificate No Extra costs Custom pricing
Customer cert HTTPSYour certificate on the CDN Yes Manage self in control panel Extra costs EV cert and/or Non-SNI possible
Token authentication Yes Secure Token Yes Self-service activation/configuration
Geo blocking Yes Country Access Policy Yes Self-service activation/configuration. Predefined and custom rules
Hotlink protectionThird parties cannot deeplink to your content Yes Referer Access Policy Yes
Basic authenticationUser logs in on the CDN to get content No Extra costs Available in a Custom/Private CDN scenario
IP white/blacklisting Yes IP Access Policy Yes Custom rules can be scripted (by support team at no extra charge)

Support

Customer support Gcore CacheFly
Documentation Yes Yes, public Yes Yes, public
Humans Yes Phone, chat and email support is free and available 24/7 Yes All customers get 24/7 email and phone support and a dedicated implementation/solutions engineer. Extra support ('Elite managed') available at a fee with SLA for support response time