GitHub
GitHub cost by product and repository, from your organization's usage report
SaaS Connects with Personal access token
Costfluent reads what GitHub bills your organization by usage, per UTC day, by product, SKU and repository. From there it feeds cost reports, cost allocation and budgets.
Permanent Free plan with no time limit
What arrives
An organization's metered usage, per day and repository
Products and their SKUs
Each product, such as “Actions”, “Codespaces” or “Copilot”, arrives as its own service, with GitHub's SKU, quantity and unit beneath it.
Repositories as resources
Usage is filed under its repository, while an organization-wide charge such as a “Copilot” seat has none. GitHub's API reports no cost per user or per workflow.
US dollars, net of included usage
Cost arrives in US dollars, the currency GitHub bills in. Billed cost is net of what your GitHub plan includes and list cost is gross, so included usage has a list cost but bills at zero.
Names doubling as IDs
The organization and its repositories arrive under their names, which double as IDs; GitHub ignores case in an organization's name, so its ID is kept in lower case.
What you do with it
From repository totals to a team's budget
GitHub cost per repository
A report grouped by resource ranks repositories by GitHub cost; group by service as well to see whether “Actions” or “Codespaces” drives each one.
GitHub repositories by team
A rule on resource name, such as “contains” a team's prefix, puts that team's repositories in its segment. Charges without a repository, like “Copilot” seats, match no such rule and stay visible as unallocated.
GitHub usage against a budget
Give GitHub cost, or one team's repositories, a budget on a saved report, and watch actual spend and the forecast against it until the period ends.
How Costfluent connects
One fine-grained token per GitHub organization
- An owner of the organization creates a fine-grained personal access token whose “Resource owner” is the organization and whose one permission is “Administration” set to “Read-only”. That also lets it read the organization's settings, never change them, so make it for Costfluent alone. The organization must be on GitHub's enhanced billing platform.
- Costfluent stores the token and organization name encrypted and makes one kind of request with them: the organization's usage report for a single UTC day. It reads no code, issues or workflows, and refuses a token that cannot read the billing before saving.
- A GitHub connection syncs once a day by default and can be set as often as hourly. Each sync rereads the latest days, picking up usage GitHub revises afterwards.
- On connecting, Costfluent requests the usage report for each day of your plan's backfill, six months at most, as far back as GitHub reports usage.
Related pages
- For engineering teams
Explain cost changes and assign ownership without a FinOps team.
- Cost reports and dashboards
Group costs by the dimensions that matter and save views for each team.
Articles on this topic
Keep every repository's GitHub cost in view
Start on the permanent Free plan; connecting takes one fine-grained token from an owner of your GitHub organization.
Permanent Free plan with no time limit