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
13 supporting · 5 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. |
| LangChain (LangSmith) | Jun 2026 | LLMops platform with 6 distinct units: seats, traces, workflow-executions, units, cpu-hours, storage-gb — an observability and evaluation platform accreting units as it ships new capabilities (traces for monitoring, storage for datasets, cpu-hours for evaluation runs). |
| LiveKit | Jun 2026 | Real-time agent infra with 5 metered units: agent-session minutes, WebRTC media minutes, inference credits, telephony minutes, and bandwidth-gb — each representing a distinct cost driver in an AI voice-agent stack. |
| Weaviate | Jun 2026 | Vector DB with 4 units: vectors-indexed, tokens (for AI-powered operations), api-calls, and storage-gb — multi-dimensional infra metering extending from GPU cloud into managed data infrastructure. |
| Anthropic | Jun 2026 | Added two new meters alongside per-token billing in one release: Claude Managed Agents bills $0.08 per session-hour of runtime (a session-runtime dimension, replacing Code Execution container-hours for agent sessions), and a research-preview Fast mode adds a premium-speed price band ($10/$50 on Opus 4.8, $30/$150 on Opus 4.6/4.7). A frontier model API accreting non-token units as it ships agent features. |
| Vercel | Jul 2026 | Surfaced four new BETA metered SKUs on one pricing page on top of its existing eight platform dimensions: Vercel Agent ($0.25/1M tokens), Vercel Services ($0.50/1M requests), Vercel Queues ($0.60/1M API operations), and Container Registry Image Storage ($0.10/GB-month). New units: api-operations and image-storage-gb-month — a platform accreting metered dimensions as it ships primitives. |
| AssemblyAI | Jul 2026 | Broke Guardrails into four separately-priced sub-meters (Profanity $0.01/hr, PII Audio Redaction $0.05/hr, PII Text Redaction $0.08/hr, Content Moderation $0.15/hr) and added Medical Mode ($0.15/hr) and Keyterms Prompting ($0.05/hr) add-ons across six product tabs — per-feature per-hour meters multiplying inside a speech-AI platform. |
| RunPod | Jun 2026 | Its new per-request Public Endpoints layer meters by request, token, OR character depending on the model — $0.05/1000 chars (Whisper V3), $0.02/megapixel (FLUX.1), $1.20/request (SORA 2 Pro video) — layered on top of per-hour Pods, per-second Serverless, and multi-node Clusters. A single vendor now spans per-hour, per-second, per-request, per-token, per-character, and per-megapixel meters. |
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.
- Fathom · Jun 2026 — AI meeting notetaker with a single unit (seats) — consumer/prosumer tools resist unit proliferation.
- Superhuman · Jun 2026 — AI email client with seats-only billing — no usage dimensions added despite AI features.
Trivia
-
Vercel meters eight distinct dimensions on its Pro plan (seats, bandwidth-GB, edge requests, function invocations, CPU, memory-GB-hours, tokens, builds) — the highest unit count for a single-vendor plan in the corpus — and added active CPU billing as its eighth unit in June 2025. The proliferation tracks directly with Vercel's product expansion: each new capability (serverless functions, edge compute, AI inference) introduced its own cost driver, and the pricing page grew to match.
-
The corpus has grown from roughly 20 distinct billing units (at 43 companies) to 34 (at 158 companies), adding units like actions (Rox), workflow-executions (Upstash), documents (Nomic), and browser-hours (Browserbase) — each representing a new product capability that has no natural mapping to an existing unit. The unit count grows with the product surface, not with the number of companies, which is why infra vendors lead the proliferation.
-
Consumer apps and the unit-proliferation trend diverge sharply: Character.ai (single unit: active users), Suno (single unit: credits), and Harvey (single unit: seats) prove that the app layer actively resists proliferation. The divergence is a deliberate UX choice — every additional billing dimension adds cognitive overhead for a buyer who just wants to know their monthly cost, so app-layer products pay a real adoption cost to add metered dimensions that infra buyers accept as normal.
-
Anthropic added two non-token meters in a single June 2026 release — a $0.08/session-hour runtime charge for Claude Managed Agents and a latency-priced Fast mode SKU — making a frontier model API, not a data/compute infra vendor, the place unit proliferation now shows up. The session-hour meter is metered to the millisecond and accrues only while a session is 'running', so the same Claude API that once billed purely per token now charges by tokens, cached tokens, batch tokens, per-tool actions, container/session time, and output speed at once.
-
RunPod (2026-06-30) is the corpus's most unit-diverse single vendor: its pricing page bills the same account by per-hour Pods, per-second Serverless workers, multi-node Cluster commits, AND per-request Public Endpoints that themselves meter by request ($1.20/request SORA 2 Pro), token, character ($0.05/1000 chars Whisper), OR megapixel ($0.02/megapixel FLUX) depending on the model — six billing bases surfaced on one page, the clearest single-vendor illustration of infra-layer metering fragmentation.
-
Vercel added four BETA metered SKUs in one 2026-07-06 release (Agent, Services, Queues, Container Registry) on top of its eight existing platform dimensions — a net +4 meters in a single capture, while the app-layer counterexamples (Character.ai, Suno, Harvey) still hold to a single unit. The infra-accretes / app-consolidates divergence widened rather than converged this cycle.
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 34 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 34 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.