Skip to content
FluxMeter
中文

Research

AI usage infrastructure landscape

A selective category model for technical buyers — not an exhaustive ranking, market-share chart, or vendor scorecard.

Last reviewed:

Classification note

Classifications are editorial interpretation of public positioning.

1. Research scope

Public product categories relevant to AI usage metering and monetization infrastructure. FluxMeter placement is modest: metering and optional control first; heuristic Intelligence is secondary.

2. Category definitions

Gateway
Proxy or route requests upstream of models; may attach metering hooks.
Classifications are editorial interpretation of public positioning.
Observability
Traces, latency, evals, prompt ops — answers what ran.
Classifications are editorial interpretation of public positioning.
Metering
Attribute usage events to customers/dimensions and roll up cost or usage.
Classifications are editorial interpretation of public positioning.
Budget / control
Allow/deny or limit spend before or during calls — optional layer.
Classifications are editorial interpretation of public positioning.
Billing
Plans, subscriptions, entitlements, and invoice lifecycle.
Classifications are editorial interpretation of public positioning.
Payments / invoice delivery
Collect money, tax, and deliver invoices — often separate from billing engines.
Classifications are editorial interpretation of public positioning.

3. Infrastructure layers

Layers are navigational — not quadrants or scores. Vendors may span multiple layers.

  • Gateway & model access

    4. Representative projects / products: In-house gateways, LiteLLM-style proxies, provider APIs

    Overlaps with metering when gateways emit usage events.

  • Observability

    4. Representative projects / products: Langfuse, Helicone, LangSmith (representative)

    Complementary to metering; not a ledger.

  • Metering & control

    4. Representative projects / products: FluxMeter; some billing platforms also expose limit balances

    FluxMeter emphasizes token metering + optional hot-path control.

  • Billing & invoices

    4. Representative projects / products: OpenMeter, Lago, Metronome, Orb, Stripe Billing (representative)

    Usage→invoice; distinct from hot-path control.

5. Where FluxMeter fits

FluxMeter sits primarily in metering with optional budget/control. Heuristic Intelligence APIs are a secondary, optional layer on the same rollups — not the organizing center of this landscape, and not a finance system of record.

6. Category overlaps

Products such as OpenMeter span metering and billing; observability tools may export usage without hot-path enforcement. Do not force every name into a single exclusive category.

7. Selection questions

  1. Do you need invoicing, customer-level usage queries, or both?
  2. Must control run on the LLM hot path, or are app-side entitlement checks enough?
  3. Must metering share one system with subscriptions/invoices?
  4. Is export into external billing first-class or example-only?
  5. Are you mistaking observability for metering or billing?

8. Methodology, limitations, sources, and review date

This landscape is selective and editorial. It does not evaluate private deployments, unpublished capabilities, pricing, market share, or vendor performance. Listed names are representative examples — not endorsements, and not exclusive category members.

Review date: 2026-08-15

Quick start Architecture Docs hub Compare OpenMeter & Lago