I wrote this after following the ongoing back-and-forth between Vercel and Cloudflare on Twitter- the benchmarks, the pricing arguments, the memes.
It struck me that the fight isn’t really about performance or cost; it’s about philosophy.
Cloudflare believes good developer experience starts with visibility and control. Vercel believes it starts with empathy and flow.
Curious how others here think about this:
- Do you prefer abstraction or transparency when building?
- Has either platform changed how you think about deploying or designing apps?
Vercel integration is really good. It reduce setting times e.g set CNAME and connect with github repository.
However setting time only happen once. So once setup, there is no much difference between cf and vercel.
As someone who usually setup vpc for deployment, vercel value offering is not much. But i do see its value for product focused deployment when operating cost still neglegible or covered by vc fund.
4 comments
[ 2.8 ms ] story [ 24.4 ms ] threadIt struck me that the fight isn’t really about performance or cost; it’s about philosophy.
Cloudflare believes good developer experience starts with visibility and control. Vercel believes it starts with empathy and flow.
Curious how others here think about this: - Do you prefer abstraction or transparency when building? - Has either platform changed how you think about deploying or designing apps?
However setting time only happen once. So once setup, there is no much difference between cf and vercel.
As someone who usually setup vpc for deployment, vercel value offering is not much. But i do see its value for product focused deployment when operating cost still neglegible or covered by vc fund.
The problem with Vercel vs Cloudflare is that they are big enough to compete with each other but can't outcompete.