Just curious, what does this offer that cloudflare's pro plan doesn't?
As time goes on, it'll become a lot clearer what I mean. The goal here definitely isn't to reproduce cloudflare.
I think the feature that's going live later tonight is a good example of something that's a big benefit to smaller sites and requires more resources: Normally, each edge node in a CDN contacts the origin server and caches the file on that node. By tomorrow morning, you'll be able to tell Nuevo Cloud that if one edge node has a cache miss, it should also tell the other edge nodes about the file so they too can cache it. Essentially, 1 cache miss anywhere in the world, and you've primed the cache on the entire network.
What that means in practice is that there's a single request for a file, and it gets transferred to 8 different locations, and stored at each location for 30 days.
It's certainly not a replacement for their DDOS/security features. Nuevo Cloud is solely about improving the performance of low/medium traffic websites. And from my testing (on both nuevocloud.com and one of my other websites), the performance is the best I've seen from a CDN (I'm clearly biased, but numbers are numbers).
I also use Nuevo Cloud (and have used other CDNs) on one of my ecommerce websites that gets a couple thousand people/day. So there's google anayltics timing stats, but those aren't the most accurate.
Of course, this is very different than the performance monitoring that's done for Nuevo Cloud. It's much easier when you have access to the actual servers to track performance stats and work to improve those (compared to trying to compare real world performance versus another CDN).
I had a few questions I don't see answers to on the landing page:
Do you support pushing to edge nodes? Do you support the Vary header across things like Accept & Accept-Encoding? Is the $25/mo for 100GB across multiple domains? Any plans for higher tiers?
Out of interest, how big is the team behind this? What's your background? Would be interested to hear of how you go about setting this up to be quicker than the competitors, and what lessons you've learnt along the way.
All in all it looks really compelling - Good luck with it.
Do you support pushing to edge nodes? Push zones won't be implemented until later this year.
Do you support the Vary header across things like Accept & Accept-Encoding? Accept-encoding is used to decide if the reply is gzip'd, but other than that no. If you email me, I'll let you know when I'm finished implementing Vary.. it'll probably be this weekend.
Is the $25/mo for 100GB across multiple domains? yes. there's no limit on the number of domains.
Any plans for higher tiers? Yes.. there will be a couple of larger plans. In the meantime, you're welcome to email me if you need a larger plan.
The team is just me. I built this because it seems like every CDN focuses on enterprises, instead of the startup type websites I usually work on. I feel like most CDNs are a catch-22.. to get good performance at the edge, your website has to be popular enough to cache... but if your website is slow, no one is going to use it, so the CDN doesn't cache it. So this actually caches your files at the edge, even in areas where your website is less popular (so you can actually build up an audience in that area of the world).
As far as the website being quicker, it uses a web app framework I've developed over the past decade + the CDN (which I wrote in Golang and C). I've worked on various startups over the past 14 years (nothing big though).