Vercel is changing how it bills for function invocations. The platform is moving from package-based pricing to per-unit pricing for Pro and new Enterprise customers, according to the Vercel changelog.
The math is straightforward. The new rate is $0.0000006 per invocation. That works out to the same $0.60 per 1 million invocations that Pro customers were already paying under the old package model. The number is not changing. The structure is.
Why does the structure matter? Package pricing means you are buying a block of capacity and hoping your usage fits inside it. Per-unit pricing means your bill tracks directly with what you actually run. If you invoke less, you pay less. There is no block to overpay for and no cliff to fall off.
Existing customers are not immediately affected. Your current rate holds until the end of your current billing cycle. Starting with the next billing cycle, the per-unit model kicks in automatically.
New Enterprise customers are also on the per-unit model from the start.
For most engineers, the immediate dollar impact is neutral if your usage stays flat. The bigger shift is in how you should think about cost forecasting. Per-unit pricing rewards leaner function usage and makes it easier to project costs against actual invocation counts rather than against a package ceiling.
What to do today: pull your current function invocation counts from the Vercel dashboard and multiply by $0.0000006. That is your new per-cycle cost baseline. If you have alerting or budget caps configured against the old package model, update those thresholds now before the next billing cycle begins. If you are on Enterprise and evaluating a new contract, confirm with Vercel whether the per-unit model applies to your tier.