Alternatives to CloudFlare logo

Alternatives to CloudFlare

Akamai, MaxCDN, Incapsula, Netlify, and Fastly are the most popular alternatives and competitors to CloudFlare.
52.8K
4.2K
+ 1
1.5K

What is CloudFlare and what are its top alternatives?

Cloudflare speeds up and protects millions of websites, APIs, SaaS services, and other properties connected to the Internet.
CloudFlare is a tool in the Content Delivery Network category of a tech stack.

CloudFlare alternatives & related posts

Akamai logo

Akamai

1.7K
155
0
1.7K
155
+ 1
0
The leading platform for cloud, mobile, media and security across any device, anywhere.
    Be the first to leave a pro
    Akamai logo
    Akamai
    VS
    CloudFlare logo
    CloudFlare
    MaxCDN logo

    MaxCDN

    1.6K
    495
    99
    1.6K
    495
    + 1
    99
    Our CDN makes your site load faster!
    MaxCDN logo
    MaxCDN
    VS
    CloudFlare logo
    CloudFlare

    related MaxCDN posts

    Justin Dorfman
    Justin Dorfman
    Developer Evangelist at StackShare · | 4 upvotes · 54K views
    MaxCDN
    MaxCDN
    GitHub Pages
    GitHub Pages
    Netlify
    Netlify
    Let's Encrypt
    Let's Encrypt
    Jekyll
    Jekyll
    Bootstrap
    Bootstrap
    jQuery
    jQuery
    Grunt
    Grunt
    Fastly
    Fastly
    #CDN
    #GoogleFonts
    #StaticSiteGenerators
    #Webperf

    When my SSL cert MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.

    What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.

    For the most part, everything went smoothly. The only things I had issues with were the following:

    • If you want to point www to GitHub Pages you need to rename the repo to www
    • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
    • I had to disable the Grunt htmlmin module. I replaced it with Jekyll layout that compresses HTML for #webperf

    Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/

    See more
    Todd Gardner
    Todd Gardner
    President at TrackJS · | 3 upvotes · 11.2K views
    atTrackJSTrackJS
    Amazon CloudFront
    Amazon CloudFront
    MaxCDN
    MaxCDN

    We migrated the hosting of our CDN, which is used to serve the JavaScript Error collection agent, from Amazon CloudFront to MaxCDN. During our test, we found MaxCDN to be more reliable and less expensive for serving he file.

    The reports and controls were also considerably better.

    See more
    Incapsula logo

    Incapsula

    1.3K
    24
    2
    1.3K
    24
    + 1
    2
    Cloud-based service that makes websites safer, faster and more reliable.
    Incapsula logo
    Incapsula
    VS
    CloudFlare logo
    CloudFlare

    related Netlify posts

    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare · | 44 upvotes · 287K views
    Firebase
    Firebase
    React
    React
    Redux
    Redux
    styled-components
    styled-components
    Netlify
    Netlify
    Gatsby
    Gatsby
    GitHub
    GitHub
    #ReactRally
    #Frontend
    #Google

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare · | 9 upvotes · 101.2K views
    GitHub
    GitHub
    Netlify
    Netlify
    Amazon S3
    Amazon S3
    Buddy
    Buddy
    Amazon CloudFront
    Amazon CloudFront
    CloudFlare
    CloudFlare
    Code Climate
    Code Climate
    #Devops
    #Webpack
    #Git
    #Gzip

    When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.

    One of the issues I had with Netlify was I wanted to gzip my JavaScript files, I had this setup in my #Webpack file, however Netlify didn't offer an easy way to set this.

    Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the content-encoding of the JavaScript files. - Buddy is also free if you only have a few pipelines, so I didn't need to pay anything 🤙🏻.

    When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there code smells, issues, and other issues I've been super happy with it so far, on the free tier so its also free.

    I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.

    See more

    related Fastly posts

    Justin Dorfman
    Justin Dorfman
    Developer Evangelist at StackShare · | 4 upvotes · 54K views
    MaxCDN
    MaxCDN
    GitHub Pages
    GitHub Pages
    Netlify
    Netlify
    Let's Encrypt
    Let's Encrypt
    Jekyll
    Jekyll
    Bootstrap
    Bootstrap
    jQuery
    jQuery
    Grunt
    Grunt
    Fastly
    Fastly
    #CDN
    #GoogleFonts
    #StaticSiteGenerators
    #Webperf

    When my SSL cert MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.

    What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.

    For the most part, everything went smoothly. The only things I had issues with were the following:

    • If you want to point www to GitHub Pages you need to rename the repo to www
    • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
    • I had to disable the Grunt htmlmin module. I replaced it with Jekyll layout that compresses HTML for #webperf

    Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/

    See more
    Cloudflare CDN logo

    Cloudflare CDN

    15
    13
    0
    15
    13
    + 1
    0
    Ultra-fast static and dynamic content delivery
      Be the first to leave a pro
      Cloudflare CDN logo
      Cloudflare CDN
      VS
      CloudFlare logo
      CloudFlare
      WP Rocket  logo

      WP Rocket

      461
      1
      0
      461
      1
      + 1
      0
      Premium Caching Plugin for WordPress
        Be the first to leave a pro
        WP Rocket  logo
        WP Rocket
        VS
        CloudFlare logo
        CloudFlare
        Amazon CloudFront logo

        Amazon CloudFront

        11.3K
        3.4K
        935
        11.3K
        3.4K
        + 1
        935
        Content delivery with low latency and high data transfer speeds
        Amazon CloudFront logo
        Amazon CloudFront
        VS
        CloudFlare logo
        CloudFlare

        related Amazon CloudFront posts

        Russel Werner
        Russel Werner
        Lead Engineer at StackShare · | 21 upvotes · 436.3K views
        atStackShareStackShare
        React
        React
        Glamorous
        Glamorous
        Apollo
        Apollo
        Node.js
        Node.js
        Rails
        Rails
        Heroku
        Heroku
        GitHub
        GitHub
        Amazon S3
        Amazon S3
        Amazon CloudFront
        Amazon CloudFront
        Webpack
        Webpack
        CircleCI
        CircleCI
        Redis
        Redis
        #StackDecisionsLaunch
        #SSR
        #Microservices
        #FrontEndRepoSplit

        StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

        Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

        #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

        See more
        Julien DeFrance
        Julien DeFrance
        Principal Software Engineer at Tophatter · | 16 upvotes · 887.4K views
        atSmartZipSmartZip
        Rails
        Rails
        Rails API
        Rails API
        AWS Elastic Beanstalk
        AWS Elastic Beanstalk
        Capistrano
        Capistrano
        Docker
        Docker
        Amazon S3
        Amazon S3
        Amazon RDS
        Amazon RDS
        MySQL
        MySQL
        Amazon RDS for Aurora
        Amazon RDS for Aurora
        Amazon ElastiCache
        Amazon ElastiCache
        Memcached
        Memcached
        Amazon CloudFront
        Amazon CloudFront
        Segment
        Segment
        Zapier
        Zapier
        Amazon Redshift
        Amazon Redshift
        Amazon Quicksight
        Amazon Quicksight
        Superset
        Superset
        Elasticsearch
        Elasticsearch
        Amazon Elasticsearch Service
        Amazon Elasticsearch Service
        New Relic
        New Relic
        AWS Lambda
        AWS Lambda
        Node.js
        Node.js
        Ruby
        Ruby
        Amazon DynamoDB
        Amazon DynamoDB
        Algolia
        Algolia

        Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

        I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

        For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

        Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

        Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

        Future improvements / technology decisions included:

        Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

        As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

        One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

        See more

        related KeyCDN posts

        RMW Web Publishing
        RMW Web Publishing
        Web Development at RMW Web Publishing · | 4 upvotes · 34.1K views
        atWashington BrownWashington Brown
        KeyCDN
        KeyCDN
        Pingdom
        Pingdom
        CloudFlare
        CloudFlare
        imgix
        imgix
        #WebpageTest
        #GoogleInsight

        Platform Update: we’ve been using the Performance Test tool provided by KeyCDN for a long time in combination with Pingdom's similar tool and the #WebpageTest and #GoogleInsight - we decided to test out KeyCDN for static asset hosting. The results for the endpoints were superfast - almost 200% faster than CloudFlare in some tests and 370% faster than imgix . So we’ve moved Washington Brown from imgix for hosting theme images, to KeyCDN for hosting all images and static assets (Font, CSS & JS). There’s a few things that we like about “Key” apart from saving $6 a month on the monthly minimum spend ($4 vs $10 for imgix). Key allow for a custom CNAME (no more advertising imgix.com in domain requests and possible SEO improvements - and easier to swap to another host down the track). Key allows JPEG/WebP image requests based on clients ‘accept’ http headers - imgix required a ?auto=format query string on each image resource request - which can break some caches. Key allows for explicitly denying cookies to be set on a zone/domain; cookies are a big strain on limited upload bandwidth so to be able to force these off is great - Cloudflare adds a cookie to every header… for “performance reasons”… but remember “if you’re getting a product something for free…”

        See more
        EdgeCast logo

        EdgeCast

        95
        22
        0
        95
        22
        + 1
        0
        The world's fastest and most reliable content delivery network.
          Be the first to leave a pro
          EdgeCast logo
          EdgeCast
          VS
          CloudFlare logo
          CloudFlare
          cdnjs logo

          cdnjs

          68
          62
          10
          68
          62
          + 1
          10
          An open source community driven Javascript CDN
          cdnjs logo
          cdnjs
          VS
          CloudFlare logo
          CloudFlare
          Google Cloud CDN logo

          Google Cloud CDN

          35
          38
          1
          35
          38
          + 1
          1
          Low-latency, low-cost content delivery using Google's global network
          Google Cloud CDN logo
          Google Cloud CDN
          VS
          CloudFlare logo
          CloudFlare
          Azure CDN logo

          Azure CDN

          20
          6
          0
          20
          6
          + 1
          0
          A global CDN solution for delivering high-bandwidth content
            Be the first to leave a pro
            Azure CDN logo
            Azure CDN
            VS
            CloudFlare logo
            CloudFlare
            CacheFly logo

            CacheFly

            16
            6
            0
            16
            6
            + 1
            0
            A leading content delivery network provider based in Chicago, IL
              Be the first to leave a pro
              CacheFly logo
              CacheFly
              VS
              CloudFlare logo
              CloudFlare
              CDNify logo

              CDNify

              12
              11
              5
              12
              11
              + 1
              5
              Content Delivery Network for tech startups, digital agencies & developers
              CDNify logo
              CDNify
              VS
              CloudFlare logo
              CloudFlare
              BunnyCDN logo

              BunnyCDN

              10
              6
              0
              10
              6
              + 1
              0
              A super cheap, but lightning fast CDN to speed up your website.
                Be the first to leave a pro
                BunnyCDN logo
                BunnyCDN
                VS
                CloudFlare logo
                CloudFlare
                CDN77.com logo

                CDN77.com

                9
                7
                0
                9
                7
                + 1
                0
                Fast, transparent and flexible content delivery provider
                  Be the first to leave a pro
                  CDN77.com logo
                  CDN77.com
                  VS
                  CloudFlare logo
                  CloudFlare