Skip to main content
GitHub bills Actions minutes, Packages storage, Copilot seats and more against one organization, so a single connection captures the lot. CostGraph reads GitHub as FOCUS 1.2 records at a grain of day x product x SKU x repository, carrying both gross and net billed cost.

​
Choose how the data reaches us

CostGraph pulls it

You supply a read-only token and we call GitHub once a day. Nothing to run.

You push it

You send us FOCUS records over the API. Credentials never leave your infrastructure.

​
Let CostGraph pull

  1. Open Settings -> Integrations and pick GitHub.
  2. Name the connection, pick the tenant these charges belong to, and enter the organization login whose billing you want.
  3. Supply a token with read access to the organization’s billing. A fine-grained personal access token needs Administration: read; a classic token needs the billing read scope.
  4. Select Connect.
CostGraph verifies the token with a short fetch before saving, so a wrong value or a missing permission fails while you are still on the form.
Credentials are encrypted at rest and used only to read billing data. Revoke the token in GitHub at any time and the connection stops; nothing else is affected.

​
Push it yourself

Send the charges to CostGraph as FOCUS records instead. Push FOCUS data covers the connection id, the focus:write key, and the request shape.

​
What CostGraph does with it

Records land as raw billing rows, are normalised into line items, and roll up into daily cost. From there GitHub spend appears in Cost Overview and in anomaly detection alongside every other provider.