The cost unit changed
Cloud spend may use a vCPU-hour or GB-month. GitHub may use tokens, premium requests, agent sessions, provisioned capacity, or seats. The billing model determines the right cost unit.
Copilot seats only earn their keep when people use them.
Connect GitHub Copilot Business or Enterprise. CloudMonitor brings adoption, seat utilization, and user-level usage into the reports your engineering and FinOps teams review.
CloudMonitor reads supported GitHub Copilot usage and billing data through an authorized GitHub token. The live reports show which tools are active, how many assigned Copilot seats are used, and which Copilot users are generating usage. GitHub remains the source of truth for current pricing and invoice totals.
- Compares assigned Copilot seats with active use and keeps the idle-seat gap visible.
- Shows Copilot adoption beside other connected AI tools.
- Lists user-level Copilot usage with the spend reported in CloudMonitor.
- Leaves seat changes, plan changes, and invoice reconciliation in GitHub.
Adoption
See whether Copilot adoption is broad or concentrated.
AI Tool Adoption ranks connected tools by active users and share of AI users. For GitHub Copilot, the report can also show period spend when the connected billing data supports it.
- Active users for each connected AI tool
- Share of AI users for an adoption comparison
- Period and provider filters for the review in front of you
Seat utilization
Put an idle-seat number into the renewal review.
Seat Utilization compares active users with assigned GitHub Copilot seats and shows the license value associated with the idle gap for the selected period. It provides evidence for a seat decision; it does not cancel or reassign licenses.
- Assigned versus active seats in one measure
- Idle-seat count for follow-up with engineering owners
- No automated seat changes in GitHub
Public demo · sample data
User review
Investigate usage and reported spend by Copilot user.
Power Users lists GitHub Copilot users with usage and reported spend. Use it to investigate outliers, then reconcile decision-bound currency in GitHub billing because usage metrics are not invoice totals.
- User-level activity for connected GitHub Copilot data
- Usage and reported spend in the same review table
- GitHub billing retained as the invoice source of truth
Public demo · sample data
Token economics
Why GitHub spend needs more than a SaaS line item.
AI cost can change when a request runs or a seat renews. Depending on the source, tokens, premium requests, agent sessions, provisioned capacity, or seats drive the bill. CloudMonitor uses available billing and usage data as cost signals you can allocate and review.
Allocate before you spend
Preserve product, team, environment, and cost-group context when a request runs. The provider charge alone may not contain enough information to allocate the cost later.
Cost per workload, not totals
A single invoice number cannot explain which work drove the spend. Connected data can show cost by team, feature, or workload. Business outcomes must come from the system that records them; Unit Economics provides the cost-per-measure view once you supply the monthly quantity.
Billing model
Vendor-controlled: plan seats and any metered AI-credit usage are billed by GitHub. CloudMonitor reports the connected data; GitHub remains the pricing and invoice source of truth.
What drives the bill
- Assigned seats: every active license adds to the subscription base.
- AI-credit usage: eligible metered activity depends on the GitHub plan and model.
- Seat utilization: assigned but inactive seats widen the renewal gap.
- Plan and account scope: available metrics differ by GitHub plan and organization or enterprise setup.
What CloudMonitor does show
- Active users and adoption share across connected AI tools.
- Assigned versus active Copilot seats and the idle-seat gap.
- User-level Copilot usage with reported spend where the connection supports it.
- No team or CloudMonitor cost-group allocation on the per-user report today.
CloudMonitor's approach aligns with the FinOps Foundation's Token Economics & SaaS working group, the emerging discipline for governing pay-per-token cost. See how GitHub spend fits into AI cost, efficiency, and ROI.
Start with seat utilization before renewal. An assigned license is not evidence of active use, and an active user count alone does not explain who is driving the usage. CloudMonitor keeps both questions in the same reporting area without changing the GitHub plan or its seat assignments.
The per-user report is not a team chargeback report. It does not allocate Copilot users into CloudMonitor cost groups today. Confirm access scopes and data availability during connection, and use GitHub billing for rates, allowances, and invoice reconciliation.
More ai & llm
Other integrations like this.
Find the seats that need a renewal decision.
Connect GitHub Copilot, review active use and the idle-seat gap, then confirm any currency decision in GitHub billing.
