Governance overview

A customer pays one invoice, but many teams, people, agents and API keys share it. Governance breaks a subscription’s usage and spend down along your customer’s own organization, so you can see who consumed what. You define the structure: departments and teams, cost centers, projects, workspaces, AI agents, API keys, or anything else your customers organize around.

​

Why governance

When you sell usage to a whole organization, its admins expect the controls they get from modern AI products:

• Usage in detail: who consumed what, at any level you define, such as teams, users, agents, API keys or models.
• Roll-ups: users add up to their team, teams to their department, and everything to the account.
• Enforcement: limits per team or per user, so one person can’t burn the whole budget.

Governance gives you the first two today, on your existing events and plans. Enforcement per team or user builds on the same entities and isn’t available yet.

​

What you can do

​

How it works

1. Define entities once for your organization. See Set up governance.
2. Tag your events with the values, for example "team_id": "eng". See Send attributed events.
3. Lago attributes each event to every level of the tree at ingestion.
4. Query attributed usage per subscription. See Query attributed usage.

​

Governance is opt-in

Governance never changes what you bill. Events without tags are billed as usual and show as unattributed, so you can start with one entity and add more later.