Vercel: Improved Infrastructure Pricing
vercel.com
vercel.com
https://vercel.com/docs/pricing
I have no idea what sort of bill I can expect with new costs for "edge network routing" or "incremental static regeneration" (neither of which I understand nor want).
Bandwidth was at least relatable to some extend. But now it looks like one needs to combine requests and client traffic as well as server traffic.
It wonder how that works if you proxy another vercel site through a vercel project. I.e. a nextjs projects proxies /docs to a docusaurus page. Because as of today the billed the bandwidth and requests twice :-(
Vercel gets a lot of shit for its pricing, but man from a developer experience standpoint, they are impossible to beat. As a developer first, devops distant fourth or fifth, it's such a pleasure when I get to work in the Vercel ecosystem and I'm happy to pay extra for them to keep improving the experience, but this reduction is welcome :)
Right now it is hope the community offerings are good enough, or create a build image from scratch myself.
Not really "developer experience that is impossible to beat".
Also checking the vercel page, they have so many investors, how do they all expect a company predicated on a JavaScript framework to be around in 10 years.
Example, it used to be when using Sitecore, most of its extensions points would be .NET, now in their SaaS products, .NET is 2nd class, if you really want to use their tooling, without filling in the gaps yourself, the answer is Next.js.
Vercel: We’re changing our pricing. Our community has told us we’re expensive. Also Vercel: Your bill is going up.
They’re giving us a 3 month grace period, but unfortunately don’t offer a breakdown of what is causing the increase.
Overall, it's really not clear how this can be optimized. It's... cache... You could have less cache writes, but it means your users see stale content, which isn't an acceptable solution.
The wording that 92% of people see smaller bills since many people host projects that aren't really being used, anyone who has traffic is going to get higher bills.
Most of our increases I assume will be the data cache pricing and the only real way to optimise that is to move data fetching out of data cache and use our own cheaper caching layer.
I’m not doubting you at all, it’s just non-obvious to a non-serious user.
Cost per cache read and write instead of lumping it all in the bandwidth bill.
My reading is that the criticism of the bandwidth egress fees and it's inevitable unfavorable comparisons has hit home.
Only they were using that bucket for more than just egress. So they are breaking charges apart and this is going to have winners and losers from their customer base.
Reminds me of cloudflare pricing. They don't charge you bandwidth but do charge for invocations and if you do the math on how they bill invocations, the egress is in there - you are not escaping it. But the press of no egress fees is nice.
* Not using SWR headers
* Putting free tier Cloudflare in front of your Vercel instance(s)
Edge Network Routing is also a bit nebulous. I would love to see this better defined, as it's not 100% clear what contributes to volume here.
"Based on the way your application uses our infrastructure, your monthly bill for team My Team is projected to go from $ 20 to $ 69 on July 22nd."
I'm surprised by this change in pricing. This will likely force me to move to fly.io. Curious if others had a similar price hike. I utilize a single "seat" for a single repository on my Team plan. This plan has around 1.1million middleware edge invocations each month. This previously was the only limit I was exceeding for many months.
It's probably a great time to explore alternatives in case of future price hikes. The new pricing plan is immensely complicated, and might take the crown from GCP in price-complication.
While ~92% of Pro teams saw a decrease with our pricing changes, I do want to acknowledge that seeing a projected increase is never fun, and I'm happy to personally jump on a call with you if you wanna talk.
That projection is based on your current usage, but you won't be charged for the new metrics for an additional three months. That gives you to ~September to optimize your site. We're confident that everyone with an increase (likely due to Edge Requests or ISR usage) can make some minor tweaks to remain flat or decrease their bill.
For example, so far from the customers I've been working with, some have already optimized their sites by changing some instances of revalidate: 1 to something higher, like 60, which reduces the number of writes you're making with ISR to the cache.
lee at vercel dot com if you want to chat.