Function invocations now billed per unit

Vercel published "Function invocations now billed per unit" in its Changelog on 2026-05-29. Without the full original text, the only thing that can be confirmed is this: it is a change related to how Function invocations are billed, and the new description is that billing is "per unit." Changes like this typically affect projects that use Vercel Functions, serverless API routes, background tasks, or event-triggered logic, because an invocation represents the number of times a function is called or executed; if the billing unit or the way usage is counted changes, the actual bill may end up tracking the call volume itself more closely. It is worth noting that the headline does not explain the per-unit price, free allowance, plan differences, scope of effect, whether it only affects new users, or whether existing usage credits are being adjusted at the same time, so one cannot infer that this is necessarily a price increase or decrease. For Taiwanese developers, SOHO operators, and startup teams, the practical move is to first treat this announcement as a cost-control reminder: check which routes, webhooks, cron jobs, preview deployments, or front-end polling in your production projects frequently trigger functions; confirm the invocation numbers in your monitoring and billing dashboards; and for endpoints with high call volume but low value, apply caching, throttling, request batching, or move the workload elsewhere. If a team is using Vercel to host an AI product, it should also note that LLM applications often involve multi-step API calls, streaming, tool calls, or agent loops, and these behaviors can cause function invocation counts to climb quickly. However, because the full announcement content is not available right now, all specific pricing and plan impacts should still be confirmed against Vercel's official Changelog and Billing pages.