SECURITY Signal 88
Vercel Sandbox now calculates snapshot storage costs daily
↗
Vercel now calculates Sandbox snapshot storage charges from each day's average usage rather than a single monthly average, applying automatically at the start of the next billing period for Pro and Enterprise teams.
The unit price of $0.08 per GB-month is unchanged, but day-to-day fluctuations in snapshot storage will now surface as discrete items on the monthly invoice instead of being smoothed into one figure. The Usage page becomes a day-by-day cost forensics surface, which makes spikes attributable but also makes the bill more variable. Because the change requires no action, the practical impact is on visibility and forecasting rather than on what teams have to deploy.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Sandbox snapshot storage billing now averages each day independently instead of across the whole month.
The published rate remains $0.08 per GB-month; only the averaging window has changed.
Pro and Enterprise teams get the new calculation automatically at the start of their next billing period with no action required.
THE READ
What the cluster adds up to.
The billing mechanic for Vercel Sandbox snapshot storage shifted from a single month-wide average to a daily average. Each day's storage footprint now contributes its own figure to the monthly invoice rather than being folded into one end-of-period number. The rate itself, $0.08 per GB-month, is unchanged - what changed is the granularity at which usage is measured for billing purposes. The shift is described as automatic for Pro and Enterprise teams, with no configuration step on the customer side.
Nothing changes at the application or infrastructure layer. Teams keep storing and retrieving snapshots as before, and the material explicitly states that no action is required. The change is positioned as taking effect at the start of the next billing period, so existing invoices are unaffected. The operational cost of adoption is effectively zero - this is a billing-system update, not a runtime change.
The places where the change has the most effect are forecasting and cost attribution. A day where snapshots briefly balloon will now appear as a higher line on the invoice even if storage returns to baseline the next day, because the daily average captures the spike rather than diluting it across a full month. Teams that relied on the smoothing behaviour of the old calculation will see more variance month to month. The Usage page is positioned as the place to watch the new daily figures, which turns it into a day-by-day cost forensics surface.
The practical response for an engineer is mostly monitoring: confirm that the new daily figures on the Usage page line up with expected snapshot retention patterns, and revisit retention policies if the new granularity surfaces an unexpected cost pattern. Because no pricing change accompanies the shift, the risk is surprise rather than a higher baseline spend. Only one feed carried the announcement, so any further behaviour - such as how refunds or credits interact with the daily calculation - is not in the material provided.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER