Unit proliferation at the infra layer
Infrastructure and platform vendors keep adding metered dimensions as they ship features — Vercel now meters eight — while consumer apps consolidate to a single credit or seat. The metering surface is fragmenting at the infra layer and consolidating at the app layer.
What's happening — and why
What's happening: infrastructure vendors keep adding new things they bill for — compute, bandwidth, storage, requests, function invocations — so one platform can meter eight or more units at once. Consumer apps move the opposite way, collapsing everything into a single credit or seat.
Why: at the infra layer each capability has a distinct cost driver, and buyers want the price to track the resource they actually control, so granular metering wins. At the app layer users just want a simple, predictable bill — so the same complexity gets hidden behind one number.
How it works
Evidence over time
6 supporting · 3 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Vercel | Jun 2025 | Active CPU billing added; now meters eight distinct units — seats, bandwidth-GB, edge requests, function invocations, CPU, memory-GB-hours, tokens, builds. |
| Vercel | Apr 2024 | Granular metering + Pro add-ons split billing into more dimensions vs the 2022 bundled-allocation model. |
| Modal | Sep 2025 | Per-second GPU/CPU/memory plus storage-GB and function invocations — five metered units. |
| ElevenLabs | May 2025 | PAYG shift spread metering across characters, credits, hours, minutes and seats. |
| Deepgram | Dec 2024 | Split into per-product STT / TTS / Audio-Intelligence tables billed per-minute, per-character and per-token. |
| RunPod | Feb 2026 | Pods / Serverless / Instant Clusters relabelled into separate metered product lines with reservations. |
Counterexamples
- Character.ai · Feb 2026 — Single unit only (active users); monetises free users with ads rather than new meters.
- Suno · May 2026 — One credit unit across Free / Pro / Premier.
- Harvey · May 2026 — Seats only — no usage metering.
For buyers
More units means more places the bill can surprise you. For infra vendors, ask which dimensions are new this year and which dominate a typical invoice; for app vendors, the single unit is simpler but often hides the same complexity behind a credit.
For vendors
A new metered dimension only pays off if you can attribute cost to it cleanly and explain it on the invoice. Each unit raises billing-system and support load — proliferate at the infra layer where customers model cost, consolidate at the app layer where they don't.
Outlook — what to watch
Infra metering will keep fanning out as new cost drivers appear (active CPU, GPU-seconds, agent steps). The countervailing force is tooling: as cost-attribution and forecasting improve, expect a swing back toward a few 'headline' units with the rest folded into bundles. Watch for vendors that lead with one number and meter the rest underneath.
Bottom line
The corpus exposes 20 distinct billing units. They fragment at the infrastructure layer (Vercel meters eight) and consolidate to a single credit or seat at the app layer.
FAQ
What is a 'billing unit' in AI pricing?
The thing you're charged for — tokens, seats, GPU-hours, API calls, credits, edge requests, and so on. The corpus uses 20 distinct ones; a single infra vendor can meter many at once.
Why do infrastructure vendors meter so many units?
Each new capability has a distinct cost driver (compute, bandwidth, storage, invocations), and infra buyers want to model cost precisely. Vercel, Modal and RunPod expose multiple units for exactly that reason.
Is more granular metering better?
For infra buyers, yes — it maps price to the cost they control. For consumer apps it's noise, which is why those vendors collapse everything into one credit or seat.