Lago has been able to follow the pace of our releases and has allowed us to focus on what we do best.

Usage Metering
Lago is the open-source billing platform that gives engineering and finance full control over any usage-based model. Event-driven metering, hybrid pricing, self-hosted or cloud.
Capture usage from every source that drives your product, from HTTP APIs and streaming connectors to AI gateways and the LLMs behind them. Lago brings events from Kafka, Kinesis, S3, GCP, Redis, Azure, and more into one real-time metering flow. Track credit drawdown as it happens, apply usage-based pricing at scale, and keep every charge visible from the first event to the final invoice.
AI gateways & LLMs
API & streaming
Ready for billing
Send events from your application with the API or a Lago SDK.
Aggregate events into billable metrics, from API calls to compute hours.
Combine usage charges, subscriptions, and prepaid credits in your plans.
Apply each customer’s plan to their usage and generate their invoice.
Bring usage from HTTP APIs, event streams, and LLM gateways into Lago. Connect sources such as Kafka, Kinesis, and your AI stack to ingest usage at scale and turn it into billable metrics.

Lago ingests raw usage data and converts it into charges. Aggregate events in real time to ensure your billing doesn’t miss a beat.

Bill as many products as you want and ingest up to 1M events per second.

Both non-engineers and engineers can update usage charges via API or Lago’s no-code UI.

Everything you need to bill for usage.

Billing is mission-critical. Lago is engineered for the realities of high-volume enterprises.
See how ambitious teams build and scale their billing with Lago.
Lago has been able to follow the pace of our releases and has allowed us to focus on what we do best.

Usage metering captures product consumption, an API call, a token, a compute-minute, as an event, then aggregates those events into a number billing can charge for. In Lago, every event carries a code that maps to a billable metric, a transaction_id for deduplication, and a subscription reference, and events arrive through the REST API, batch API, streaming connectors, or an S3 backfill.