I just got off the phone with a reporter. Like many reporters or analysts we talk to, she wanted to put CloudFlare into a defined category. Specifically, she wanted to call us a content delivery network (CDN) and compare us with companies like Akamai (at the high end) or Amazon's CloudFront (at the low end). While I hemmed and hawed about how we have more than 10x the number of customers as the two services combined, the real problem is that "CDN" isn't an accurate and complete description of CloudFlare. So I'm left with the puzzle: what are we?
CDN Is A Feature
It is true that CloudFlare uses CDN-like technology in order to do some of the things we do. Like a CDN, we run multiple data centers and cache static content at the edge in order to make it faster. Traditional CDNs, however, only receive the requests for some subset of requests and require users to choose what content to host on the CDN's network. Traditional CDNs can be accurately described as massively distributed hosting, where CloudFlare is more accurately described as a caching reverse proxy. What this means is that, unlike traditional CDNs, CloudFlare handles all requests to a website. As a result, we are able to:
- Stop attacks directed at a website
- Dynamically modify content in order to improve performance
- Insert applications into web pages
- Provide rich analytics on all the requests to your website
- Automatically determine what objects are static and cacheable at the network's edge without any user configuration
- Provide a network gateway between protocols like IPv6 \<-> IPv4
- Make installing SSL flexible and one-click easy
- And many more things a traditional CDN can't provide....
One test of whether a category thoroughly describes a product is to ask whether using one product already in the category would exclude the use of another product proposed to be in the category. In our case, we have many customers that use CloudFlare in conjunction with traditional CDNs, including Akamai and CloudFront. In other words, we think of CDN as a feature that we include by default, but if you'd prefer to use another CDN then that'll work just fine too. And there's this: today there are more websites using CloudFlare than all traditional CDNs combined.
More than a year after our public launch we're still struggling to find a category that accurately describes what we do. An analyst recently asked: "What do you call the category CloudFlare fits in?" I said, "I
have no idea, I thought it was your job to tell me." We laughed but, unfortunately, his report didn't suggest anything other than "Next Generation CDN." I think we can do better.
So, I thought, maybe CloudFlare's users could come up with a name for the category. Ideally something catchy and short while still being descriptive and accurate. Suggest your ideas in the comments and we'll see if anything sticks.