Pro customers move from $0.60/1M invocations to $0.0000006 per invocation, reducing upfront consumption of monthly credits on low-volume usage.
June 9, 2026
Summary
Per-unit billing directly ties costs to actual invocations, letting teams on Pro tier use functions without burning through included credits on variable workloads. This surfaces real usage patterns earlier and may reduce bill surprises for scaling applications.
Why it matters
Per-unit billing directly ties costs to actual invocations, letting teams on Pro tier use functions without burning through included credits on variable workloads. This surfaces real usage patterns earlier and may reduce bill surprises for scaling applications.
Implementation verdict
Replaces fixed package pricing with granular per-invocation charges. No code changes required; takes effect next billing cycle for Pro and new Enterprise customers. Worth auditing your invocation volume now to model cost impact—the math favors sparse, on-demand patterns over sustained throughput.
Sources
Dev Signal
Get briefs like this in your inbox — free, every weekday.
100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.