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

1–3M events/sec
Kafka/Redpanda + ClickHouse Cloud benchmark
99.9% historical uptime
Guaranteed SLAs for enterprise customers
$829M of invoices issued monthly*
Battle-tested platform, built for accuracy
*based on total requests to Lago API in October 2025
Combine billing and feature flags to avoid bugs and dependencies, reduce complexity and lower and engineering overhead.

Lago lets product and growth teams manage feature access and update pricing to optimize adoption and revenue.

Lago lets you customize multiple seat tiers, amounts and account details. Or override feature access for enterprise customers.

Billing is mission-critical. Lago is engineered for the realities of high-volume enterprises.
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.

Entitlements are the feature access rules tied to a customer's plan or subscription, managed in the same system as billing instead of a separate feature-flag service. In Lago, a feature represents a capability gated behind a plan, and an entitlement is what maps that feature to a specific plan or subscription with its own limits.
A feature is a capability a customer gains access to through their subscription, like inviting team members, and isn't necessarily something billed for directly. A privilege adds granularity inside that feature, defining a specific limit or setting, such as the maximum number of invitations, and can be a boolean, an integer, a string, or a predefined option depending on what needs to vary by plan.
Plan-level entitlements attach features to a plan and set each privilege's value for that tier. A Free plan might cap invited members at one, while a Pro plan allows unlimited, all configured from the plan's settings rather than in application code. Changing a plan's entitlement updates access for every subscriber on that plan.
Yes, through subscription-level overrides. An override changes a feature's privilege value for one specific subscription without touching the underlying plan or affecting any other customer, which is how negotiated enterprise contracts get their own limits without needing a separate plan.
Keeping entitlements and billing in one system avoids the sync problem where a customer's paid access and their actual feature access drift apart across two tools. When a plan or subscription entitlement changes, it comes from the same source of truth that generates the invoice, so a plan upgrade or downgrade updates feature access without needing a parallel update in a feature-flag service.
Yes. Feature, plan-entitlement, and subscription-entitlement objects are all available through the API, so an application can check what a customer is entitled to and reflect it in the UI directly, and track changes as plans or overrides are updated.
Entitlements apply to whatever a plan is built from, flat subscription, usage-based, or hybrid, since they're a layer on top of the plan rather than tied to one pricing model. A usage-based plan can gate a feature the same way a flat-fee plan does.