CloudFlare vs. Akamai vs. MetaCDN

Provides our CDN for hosting our front-end Angular powered interface.

Hosts our DNS, load balances our traffic, and provides CDN capabilities.

Great for performance and security. Now offering free SSL for modern browsers, how could we not love CF?

We manage our DNSs, precaché our static files and block out malicious traffic

CDN and Performance improvements

Free account used for 301 redirects from http://www.habdas.org to http://habd.as, to add resource caching headers and to optimize site performance.

CDN for scripts.

DNS Hosting for all of our customers we don't need to worry about our own DNS Servers.

Railgun Optimizer, CDN Cache and Free SSL of course.

We use CloudFlare to manage our DNS. The added performance and security is a plus.

We use CloudFlare as a DNS provider, as a CDN and for its page rules, e. g. to enforce HTTPS for certain domains.

DNS and network performance

As a CDN

Naked domain, free ssl

CDN, email guarding, DDOS protection, hiding ports

DNS, absorber for large spikes in traffic

dns manager for my google domain. free ssl and analytics.

We use CF for DNS hosting, since their AnyCast DNS provides the best latency in the business, and they support DNSSEC + IPv6. We don't use the CDN or website optimizations.

Https, simple CDN and damx fast DNS record updating

Cloudflare sits in front of the entire site providing HTTP2 and HTTPS, which is particularly important due the large number of SVG images for the headings that need to be send down to the browser in parallel. Cloudflare also manages the DNS for DKIM TXT records, a dynamic root ALIAS record to the Heroku application, and GeoIP country headers.

Cloudflare is used as a global cache for performance and security.

Delivers content in a fast and secure way.

We use it as our CDN and extra security stack.

The Console, Website and API gateways are all protected by CloudFlare.

DNS management and API.

Handle DNS requests, free SSL and faster page load times

It is the CDN of security.

Domain Name Server as well as IPV6 compliance.

I have limited experience with CloudFlare, but it has a great reputation and having a good focused CDN to rely on is paramount for high-availability apps.

Caching, SSL, traffic analytics

DDoS protection, DNS management, and SSL.

lots of good stuff available for free that you don't even think about it, default configuration saves you weeks of work, painless https setup, good to kickstart projects

Cloudflare functions mostly as a simple CDN to our website. Most of requests delivered to our server don't even get through Cloudflare, and we could easily do without.

CDN, SSL,

CDN and DDoS protection

Used to add SSL, DDoS Protection, Control DNS, and Edge Caching

CDN and security.

helping us delivery our rapid order process even faster.

We love the free SSL and extensive CDN network. DDoS protection is a plus. Great premium features for rapidly growing projects. Cloudflare has helped us forget about silly things like asset minification and email obfuscation.

CloudFlare is used for SSL and DNS because it is so simple to manage and also secures our infrastructure against mal-intent.

DNS resolution

Fast and secure dns with lots of performance and secure features

To accelerate bandwidth to edge locations for non cloud hosting. On the AWS cloud, I use CloudFront instead.

I love the caching, SSL and security that CloudFlare provides.

As a second layer of caching in front of Cloudfront CDNs and our own API responses. Quite frankly, without Cloudflare's support we'd be bankrupt.

Cloudflare protection as well as the DNS stats

We use CloudFlare to protect our network from breaches as well as to reduce bandwidth on the servers themselves and therefore freeing up the bandwidth for our other projects. We also use CloudFlare for instant DNS propagation across the internet where possible.

No frills security.

CloudFlare is used as CDN and statistics tracker for https://shiro.host/, our public development and testing server.

Akamai sits at the front of the site, all assets and pages are cached for a minimum of 60 seconds. Requests to the edge peak at over 100k/s.