COMPARE
Per-line attribution is just the start. Iria Monitor adds the LLM cost proxy, the live dashboard, the burndown, the menubar, three SaaS views and a multi-vendor enterprise comparison — none of which the alternatives ship.
Built on the open git-ai standard. Compatible with everything else.
Engineering intelligence
Measure team velocity
The open standard
Defines how AI authorship is stored
Complementary gateway
LLM API gateway with spend tracking
The complete toolkit
Everything teams actually need to manage AI coding
The gap we close
Engineering intelligence measures your team.
git-ai defines the attribution standard.
LiteLLM tracks the API spend.
Nobody else ships the toolkit.
Iria Monitor annotates each edit with its exact API cost in the git note. LiteLLM tracks spend per request — we track spend per line of code that survives.
HEAD TO HEAD
git-ai is the open standard. We use it. But that's where the similarities end — Iria Monitor ships 17 capabilities that git-ai doesn't.
Iria Monitor
capabilities shipping today
git-ai
capabilities (just the standard + CLI)
What Iria Monitor ships
Attribution (the foundation)
Cost & usage observability
Dashboards & UX
Integration & deployment
Free tier
What git-ai ships
Attribution (the foundation)
Cost & usage observability
Dashboards & UX
Integration & deployment
git-ai is excellent at what it does — defining and storing the open attribution standard. Iria Monitor is the toolkit you build on top of it.
Based on public information from each vendor's website (April 2026)
| Capability | Iria Monitor | git-ai | LiteLLM | Exceeds AI | DX | LinearB | Faros |
|---|---|---|---|---|---|---|---|
| Attribution core (the open standard) | |||||||
| Per-line AI attribution | ✓ | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ |
| Open standard (git-ai v3.0.0 git notes) | ✓ uses it | ✓ defines it | ✗ | ✗ proprietary | ✗ | ✗ | ✗ |
| Detect agent + model (Claude / Cursor / Codex / Windsurf) | ✓ all 4 | ✓ all 4 | ~ partial | ~ partial | ~ | ~ | ~ |
| The toolkit on top — what no other tool ships | |||||||
| LLM cost & usage proxy (mitmproxy plugin) | ✓ | ✗ | ✓ | ✗ | ✗ | ✗ | ✗ |
| Cost per developer / repo / branch / model | ✓ | ✗ | ✓ per key/team | ✗ | ✗ | ✗ | ✗ |
| Live SSE dashboard (real-time activity) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Weekly budget burndown chart | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| System tray app (macOS/Win/Linux) — live AI % indicator | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| CLI: ai-stats, ai-blame, doctor (11 commands) | ✓ | ~ blame only | ✗ | ✗ | ✗ | ✗ | ✗ |
| Per-edit cost attribution in git notes | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| LLM gateway with budget enforcement | ~ transparent proxy | ✗ | ✓ core feature | ✗ | ✗ | ✗ | ✗ |
| Dashboards & analytics | |||||||
| Three SaaS dashboards (Enterprise · Vendor · Personal) | ✓ | ✗ | ✗ | ~ one view | ~ team only | ~ team only | ~ team only |
| Multi-vendor enterprise comparison (buyer view) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Per-developer private view | ✓ | ✓ local CLI | ✗ | ✗ | ✗ | ✗ | ✗ |
| Three KPIs (Adoption · Durability · Churn) | ✓ | ~ basic | ✗ | ✓ | ✗ | ✗ | ✗ |
| DORA / SPACE / cycle time | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ |
| Integration & deployment | |||||||
| GitHub App (push-based ingest) | ✓ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |
| Self-hosted on-prem option | ✓ | ✓ CLI only | ✓ | ✗ | ✗ | ✗ | ✓ |
| Source code never transmitted (metadata only) | ✓ | ✓ | ✓ | ~ | ~ | ~ | ~ |
Single install: pipx install iria-monitor |
✓ | ~ cargo install | ✗ Docker/pip | ✗ SaaS only | ✗ SaaS only | ✗ SaaS only | ✗ SaaS only |
| Pricing & access | |||||||
| Free tier for individual devs | ✓ full toolkit | ✓ CLI | ✓ open source | ✗ | ✗ | ✗ | ✗ |
| Pricing (per dev / month) | €0 / €19 / Custom | €0 / Team / Ent. | €0 / Enterprise | Contact | Contact ($$$) | Contact ($$$) | Contact ($$$$) |
✓ = supported · ~ = partial / unclear · ✗ = not supported · Sources: vendor public sites, April 2026
The honest distinction
git-ai is the open standard. Iria Monitor is the toolkit that runs on it.
git-ai defines how AI authorship is stored in refs/notes/aiand ships a CLI to read it locally. That's a great foundation — and we use it. Iria Monitor adds everything an organization needs
Iria Monitor bridges the gap: we annotate each edit with its exact API cost directly in the git note. When you run iria-monitor blame, you see not just who wrote each line (human or AI), but what that specific edit cost. LiteLLM can feed upstream spend data; we connect it to the code that was produced. The two tools are complementary — LiteLLM as the gateway, Iria Monitor as the outcome layer.
Microsoft Copilot Power BI is the system of record for adoption. Iria Monitor is the system of record for outcomes.
Microsoft is the source of truth for adoption, engagement, model usage and Copilot Studio MCP transcripts. We do not duplicate any of that. We add the outcome layer — per-line attribution at the commit level, durability over time, the wasted-agent-work KPI — that Microsoft structurally cannot publish themselves. The two datasets coexist in the same Power BI workspace. Read the full Microsoft positioning →
BUILT TO PAIR WITH MICROSOFT COPILOT
Microsoft Copilot Power BI ships excellent adoption telemetry through the AppSource template, the Viva Insights M365 reports, and Copilot Studio analytics. Iria Monitor extends that picture with the outcome layer — what landed in git and what survived. Two telemetry layers, one workspace, the complete conversation.
MICROSOFT COPILOT — ADOPTION LAYER
Engagement & reach
Model & feature usage
Copilot Studio agents
M365 productivity
The Microsoft layer answers:"How is the team engaging with Copilot?"
IRIA MONITOR — OUTCOME LAYER
What lands in git
What survives over time
Vendor & team accountability
Per-line cross-correlation
The Iria Monitor layer answers:"How much of what they ship is still in production?"
Together, both layers are what every CIO running an AI program in 2026 needs in front of them.
The Microsoft layer keeps your existing Power BI workspace as the source of truth for adoption. Iria Monitor ships as a Power BI semantic model that lives next to it as a second data source — same workspace, no migration, no replacement, compatible with Power BI Premium and Microsoft Fabric. The customer gains the outcome conversation that the Microsoft AE has been asked about repeatedly in QBRs. Read the full Microsoft pairing positioning →
Use DX / LinearB / Faros if
Use git-ai if
Use Iria Monitor if
Honest note
Iria Monitor is built on the open git-ai v3.0.0standard. We don't compete with it — we build on it. Your attribution data lives inrefs/notes/ai, the format is portable, and if you ever want to stop using Iria Monitor you can read your data with any git-ai tool. The same data portability is not available with the other vendors listed here.
Free CLI. Eleven commands. One install. Two minutes.
Get started See the toolkit