Works via DNS. Takes about 5 minutes to sign up. Tens of thousands of sites using the service. Currently powering than 2,000 page views per second for more than 100 million unique visitors per month.
Definitely make this the front page, made things a lot clearer. It could still use work, though: it still feels a bit vague on how much its oriented toward caching (which I really need to know as it could potentially require changes in a web app) and security (because I'm really confused as to why someone would want to depend on the caching proxy layer for XSS protection).
Also, this line really put me off:
> We have designed the system to scale with our goal in mind: helping power and protect the entire Internet.
I don't think anyone wants one entity having the ability to re-route a significant proportion of http traffic!
I disagree, it took a follow-up question to get the real answer to what it is. (A caching reverse proxy.)
I undertand that you'd never ever say the words 'caching reverse proxy' to normal people, but if someone on HN asks 'what is this doing' you can probably feel safe to use the technical terms.
Good ad copy, if you're aiming at geeks and only geeks, doesn't spare the jargon.
Does it serve cache hits via a CDN, or do you provide all the bandwidth?
I hadn't thought of this before reading this thread, but a great service would be something like Varnish that's backed by some CDN instead of a big block of memory. That way, we can get great performance out of sites that are low on memory and bandwidth, like your low-end Linode or Slicehost.
That's a good description: Varnish + CDN (+ security). CloudFlare ends up making sites twice as fast and saving sites about 65% of their bandwidth. We run our own CDN with nodes scattered around the world.
