Improved Pricing

[amyegan]

We’re updating our pricing and metrics next month based on your feedback. This update makes our infrastructure pricing more transparent and scalable.

• The free tier is here to stay.
• For most Pro and Enterprise customers the price stays the same or gets lower.
• Smaller usage increments give you more control to understand and optimize usage.

You can find more details in the announcement blog post and on our new pricing page.

If you have general questions or feedback about this change, please comment here or start a new discussion. For questions specific to your Pro or Enterprise plan, please submit a case so our billing experts can help you.

[raferdev]

Okay, if that's not the best way to prove that Vercel stays concerned about your users experiences I'm a capybara. Good notice!

[shawnlong636]

Man, I panicked for a second thinking Vercel was going to pull a PlanetScale and drop the free tier. 😵‍💫😅

[amyegan]

Not a chance! We love hobby projects and open-source development way too much to even consider taking away the free tier.

[ipg0]

Thank you Vercel for staying accessible, my useless garbage hobby projects wouldn't live without you lot

[z4nr34l]

I can notice that there is big inconsistency between multiple projects „Edge Requests” usage. Even very, very similar project are making much different usage. In My test case smaller app (Lets call it X) is making around 25k Edge Requests daily, when bigger one (Lets call it Y) is making only 800 edge requests. The point is that X have no logs (as there is almost no traffic) and Y have almost perfect 1:1 ratio with logs from Axiom (Log Drain). This issue persists for any deployment on Hobby and Pro tier. Hope that anyone will look into that as it’s pretty bad sign that we can’t trace from where are those request, to which resource etc. There is currently no way to trace/debug and optimize this metric usage on Vercel :(

[leerob]

When you look at "Requests" under "Top Paths" on the Usage page, what does it say?

[z4nr34l]

@leerob already got to solve that on my end:

On top paths was only domain with root path /, so it told nothing about the traffic origin.
There is no "free" way to check the requests origin/agents to get the real information.
I've solved that using trial and error method in below linked comment.

https://github.com/orgs/vercel/discussions/6640#discussioncomment-9259960

Feature request:

Option 1: Add Monitoring free usage limits on hobby/pro
Option 2: Pass literally every request to log drains (for example Axiom)

So we would be able to diagnose such situations on our-own without hours of waiting to check how it really affects this metric.