I love developing on Vercel, but this is an absurdly complicated pricing structure:<p><a href="https://vercel.com/docs/pricing" rel="nofollow">https://vercel.com/docs/pricing</a><p>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).
Awesome!<p>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 :)
Vercels hosting is ok. I prefer cloudflare and AWS but vercel is still best for next.js first class support. Especially on newest versions. For instance, server functions currently don’t work on cloudflares nextjs hosting. There’s some discussion about it on discord and GitHub. However, once something becomes the new fad and takes over from nextjs, I’m not sure what vercel will do.<p>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.
Just got the email from them explaining the changes. It goes like this.<p>Vercel: We’re changing our pricing. Our community has told us we’re expensive.
Also Vercel: Your bill is going up.
Also seeing a 400% increase in pricing after this.
Mostly due to cache reads / writes if I had to guess, the dashboard isn't showing any data currently.<p>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.<p>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.
The tone of the email was a bit strange for a $960 a year increase suggesting we optimise but not yet providing what the cost increases are from. I appreciate we will get the updated usage metrics later in the month but it makes it slightly hard to explain to management why costs are increasing.<p>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.
ISR is just a fancy way to say Cache Hits with SWR headers? So you can mitigate most of the Read cost by either:<p><pre><code> * Not using SWR headers
* Putting free tier Cloudflare in front of your Vercel instance(s)
</code></pre>
You can improve the Write cost by having longer SWR cache durations. Folks that are seeing a cost increase likely have high traffic volume, a short SWR duration.<p>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.
Just received this in my email.<p>"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."<p>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.
3x price increase for our team. Not a happy camper, mostly because I have no idea from where.<p>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.
Would now be a good time to say <a href="https://developers.cloudflare.com/workers/platform/pricing/" rel="nofollow">https://developers.cloudflare.com/workers/platform/pricing/</a>