Ask HN: Why is Vercel so expensive?
Vercel charges low/mid five figures for their enterprise plans, which essentially comes with higher usage limits, some security features like SSO and IP blocking, and an uptime and support SLA. This hardly seems worth the additional cost?
It seems like they need a much better solution somewhere in the mid-tier--Vercel is great to get started on projects, but if you basically need to go from small project to 5 figure bill without much in between, it hardly seems to make sense to use for a project that is going to scale.
23 comments
[ 2.8 ms ] story [ 33.8 ms ] threadHigher usage can be purchased separately from Enterprise, not as cheap as the initial plan, but far from 5-figures: https://vercel.com/docs/limits/overview#additional-resources
So really we're mostly talking about SLAs. I think "we absolutely need an SLA" seems a decent way to differentiate between small businesses and enterprise businesses.
The other dilemma for them seems to be in capturing true enterprise customers...if you have those resources, you might just decide to build out your own dev ops/infra team instead of paying big markups on AWS/Cloudflare bills.
I think your second point is debatable. We used to spend something like $50-100k a year on Heroku which is technically way overpriced, but hiring even a single devops person to move us to AWS would have been much more expensive and introduced all sorts of risk. I think a medium sized company is fine paying $100-300k to something like Heroku as long as the offerings are fitting the architectural needs. And Heroku is AWS so you can always use some AWS services alongside your Heroku stuff.
But for large companies making millions or billions it’s a convenience that saves engineering costs.
If you're big enough to need the Enterprise plan, sure, you could build your own, but apparently enough of their customers don't want to.
FWIW, because of Vercel, I would personally never launch another website on a lower level cloud host (like EC2/S3) again. It's just not worth the time and setup. The higher level of abstraction that Vercel, Cloudflare Pages, etc provide is very nice for DX and time savings.
The poster asked about the enterprise tier.
Do you put a team of a few devs / million plus dollars per year or 50k.
Never had any issues with upgrades/downtime for over a year now - it's pretty fire and forget.
Native vercel serverless functions running in Vercel are also highly restricted (10 seconds in hobby, and no more than 60 seconds in Pro) which I also don't have to worry about.
That seems like a pretty big pain, though, compared to a single click on Vercel and you get that same functionality for free. What's the advantage of doing it yourself? Each of those steps is quite a lot of work (few hours the first time? sure you can automate it for reuse later, but it still sounds much more of a hassle than the nice Vercel GUI). And what happens when part of the stack needs updates? (The VPS, or DOcker, or a Github action or one of its dependencies, or Nginx, or the firewall, or the rules...)
> Native vercel serverless functions running in Vercel are also highly restricted (10 seconds in hobby, and no more than 60 seconds in Pro) which I also don't have to worry about.
That's a looooong time for a serverless func to run. Curious, what do you use them for?
I also just don't like handing the keys to the kingdom over to Vercel as it were (just a personal preference really). I'm working on migrating over to a privately instanced Gitea so that I don't have to depend on Github either for my deployments but that's still in the works.
So I actually use serverless functions as ad-hoc "workers" if I don't feel like setting up a full fledged backend API - so sometimes they'll be working for upwards of a minute on a request and then lodge the final results in a notification-redis. It's not really what serverless functions are intended for, but... it's nice to sometimes not have to deal with building an entirely separate backend.
Since I control the VPS, I can easily spin up more resources to scale without worrying about Vercels payment options. It also makes it easier to migrate somewhere else if I want to since its dockerized - trivial to move to Google Cloud, Digital Ocean, AWS, etc.
A friend of mine whose project sort of blew up and went viral also said that while the autoscalibility of Vercel was very nice - it was a bit of a double edged sword, he mentioned that it was extraordinarily difficult to figure out which routes and files werer contributing to his high usage on his bill. Maybe things have changed, that was a few years back.
I've hosted many sites on Vercel and never noticed issues or significant downtime on any of their plans, Enterprise or Pro.
It seems to me that their other plans are basically loss leaders for their Enterprise offerings, but if you're a solo dev or small biz prototyping something, there is no need to go enterprise yet.
Let me know if you have any questions.
https://vercel.com/blog/improved-infrastructure-pricing