Put a project behind every dollar
Spend concentrated in one product repo tells a very different story from spend scattered across fifty.
Where the investment lands
Repository impact
See which projects your AI spend actually built, and which ones quietly absorbed it.
Why it matters
Impact depends on where the work landed
Set your repo list once
Name the repositories that carry real work. Everything else is reported separately, with its token volume.
See who drove it
Top contributors per repository, with cost, sessions and models, so credit and spend land on the same people.
How it works
How repository impact is measured
Configure repo settings
Declare the repositories you manage. One list, edited in the product, no ticket to anyone.
Sessions are matched to repos
Each session's repository is checked against that list and tagged managed or unmanaged as it arrives.
Trend it over time
Watch how the split moves, drill into the repositories and people behind it, and alert when spend drifts away from the projects that matter.
AI ready at scale
Observability that was built for AI,
Observability that was built for AI,
not repackaged for it
Run your agents and teams on the right foundation, so they don't approximate, they know
14 days, all features, no credit card required.
<1msAlert detection time
99.9%Platform uptime
10xData ingestion capacity