GitHub

Vantage ingests GitHub costs through the GitHub Enhanced Billing API. With this integration, you can programmatically grant Vantage access to GitHub billing data for multiple organizations.

​

Supported Services

Vantage supports the following GitHub services:

• Actions
• Large File Storage
• Copilot
• Codespaces
• Shared Storage
• Packages
• In addition to these services, you can also use existing Vantage tagging capabilities to track the underlying compute costs for self-hosted runners that run on a virtual machine, such as an EC2 instance, or in Kubernetes.

​

Migrate to the New GitHub Billing Integration

Previously, Vantage ingested GitHub costs using a Vantage-owned billing manager account that customers added to their GitHub Organization or Enterprise (released in September 2024). This approach required users to manually invite a billing email address, which had limitations, such as incompatibility for organizations who use SSO authentication. The second version of this integration (released in March 2025) uses the GitHub Enhanced Billing API. Any Vantage customer that is using GitHub services today and has been migrated to the Enhanced Billing API can use the new integration. GitHub started migrating customers to their new billing platform in September 2024, with all accounts being migrated by the end of March 2025. See the Prerequisites section below for instructions on how to validate if you’ve been migrated.

​

How Vantage Integrates with GitHub

The Vantage–GitHub integration requires the Billing - vantage-sh GitHub application added to your GitHub organization. Once installed, Vantage can access cost and usage data through the Enhanced Billing /usage API, which provides structured cost data for GitHub Actions, such as build minutes by user and repo, as well as the associated infrastructure used to perform the build. You can see cost and usage, such as per-repository billing for Actions, Copilot UserMonths, Copilot AI Credits with the AICredits usage unit, and GigabyteHours of Shared Storage. To allocate the infrastructure costs for your self-hosted runners, you can create a Cost Report that includes both GitHub costs and the related EC2 or EKS costs, based on tags or labels.

​

Connect Your GitHub Account

Follow the steps in this section to install the Billing - vantage-sh GitHub application and ingest GitHub costs into Vantage.

​

Prerequisites

You must be a GitHub Organization Owner to install the Billing - vantage-sh GitHub application. You must also have been migrated to the GitHub Enhanced Billing API. The new GitHub Enhanced Billing platform is available to:

• All enterprise accounts, and their organizations, created after June 2, 2024
• Enterprises that participated in the public preview program
• Enterprises that have received a notice 30 days before their migration (see the GitHub blog)

To validate that you have been moved to the Enhanced Billing Platform:

• Navigate to https://github.com/enterprises/{name}/billing (for Enterprise accounts) or https://github.com/organizations/{name}/billing (for Organization accounts), and you should see the new billing platform.
• You can also navigate to https://github.com/enterprises/{name}/settings/billing (for Enterprise accounts) or https://github.com/organizations/{name}/settings/billing (for Organization accounts). You should see a warning at the top of the page, indicating that the page has been deprecated.

Click to view example image

• You must have a Vantage Organization Owner or Integration Owner role to add or remove this integration. See the Role-Based Access Control documentation for details.
• Create a free Vantage account, then follow the steps below to connect to GitHub.

​

Create the Connection

To complete the integration, you will add the application to your organization and set up the Vantage integration in the console. After completing the OAuth flow, you will see the status of your integration change to Importing within the Vantage console. This status indicates that Vantage is actively importing your GitHub cost data. See the Integration Status documentation for details on integration statuses.

​

Next Steps - Manage Workspace Access

Once the import is complete and the integration status changes to Stable, you can select which workspaces this integration is associated with. See the Workspaces documentation for information.

​

Previous Integration (Pre-March 2025)

Any historical data you previously ingested into Vantage (prior to March 2025) is accessible only via the previous form of the GitHub integration. Once GitHub migrates you to the Enhanced Billing API, the previous Vantage GitHub integration will stop receiving updated data, as Vantage is no longer able to retrieve the CSV that was being used for cost and usage data. You can leave your previous integration connected to Vantage for historical billing data if you want to retain this information. On the integration settings page in Vantage, previous integrations are labeled Read Only. Enhanced Billing connections have no label.

​

Copilot Costs by User

Vantage can break down the Copilot AI-credit charges on your GitHub bill by person, model, token type, and GitHub cost center. The breakdown comes from GitHub’s own per-user billing and AI-credit usage reports, and it only divides the Copilot costs Vantage already imports from your GitHub bill, so your totals do not change.

​

Copilot Prerequisites

Before you connect your enterprise, make sure the following requirements are met:

• The GitHub integration must already be connected, using the Enhanced Billing integration, for the GitHub organization that holds your enterprise’s Copilot AI-credit charges. A previous integration, labeled Read Only, cannot be enhanced.
• Copilot must run through a GitHub Enterprise Cloud enterprise on github.com. Organizations that are not part of an enterprise account cannot connect, and their Copilot costs stay as organization totals. Enterprises that use GitHub Enterprise Cloud with data residency (GHE.com) are not supported.
• An enterprise owner must install the Vantage GitHub Copilot App on the enterprise, and the GitHub user who connects it in Vantage must have access to the enterprise’s billing.
• In GitHub, an enterprise owner must set Copilot usage metrics to Enabled everywhere in the enterprise’s AI controls > Copilot settings. See GitHub’s documentation on managing Copilot policies for your enterprise for details.
• You must have a Vantage Organization Owner or Integration Owner role to connect or disconnect your GitHub enterprise. See the Role-Based Access Control documentation for details. Other users can view per-user Copilot costs according to their existing workspace and Cost Report permissions.

​

Permissions

The Vantage GitHub Copilot App has two read-only enterprise permissions:

• Enterprise billing: Reads per-user Copilot AI-credit charges and requests the enterprise’s AI-credit usage report.
• Enterprise Copilot metrics: Reads the daily list of Copilot users.

The App has no access to repositories or code and cannot change settings, policies, or seats. Vantage never receives prompts, completions, or code. GitHub’s billing and usage reports contain users, models, token counts, AI credits, and cost centers. If your enterprise has an IP allow list enabled, add the Vantage IP addresses listed above to the enterprise allow list.

​

Connect Your Enterprise

To connect your GitHub enterprise and install the Vantage GitHub Copilot App, follow these steps: Per-user Copilot costs appear after the next GitHub data refresh.

​

What Changes in Your GitHub Costs

After you connect your enterprise, totals by day, organization, and category stay the same. Some GitHub costs gain per-user detail, and others are unchanged: Copilot model usage is billed in AI credits by GitHub and appears only under your GitHub integration. It is not double counted with your OpenAI, Anthropic, or other AI provider integrations, which only include usage billed to those accounts.

​

How Per-User Amounts Are Calculated

Each person’s cost by model and day is what GitHub billed that person, including any discount GitHub applied. In rare cases, the per-user amounts GitHub reports add up to slightly more than the bill, usually by cents. Vantage then scales them down in proportion so they sum to the billed total, and no one’s discount is larger than their usage. Charges that GitHub does not assign to a user stay on an unattributed row for that model and day, with no user tags. Vantage never spreads them across users, so totals always match the bill. The token-type split is derived. Vantage works out each model’s per-token rates from GitHub’s AI-credit usage report, checks them against GitHub’s published Copilot pricing, and splits each charge by tokens times rate, so the parts always sum to the billed charge. A few charges are handled differently:

• When GitHub billed a model at its higher long-context rates, the extra amount appears under the Long Context subcategory. See the note below.
• When Copilot selected the model automatically (Auto), GitHub does not publish the discount it applied, so those charges are split in proportion to tokens as an estimate.
• Code review charges, and models without a published price, stay as one row per person and model.

Cost Reports show Copilot costs and AI credits (the AICredits usage unit) broken down by token type, but not token counts. Vantage uses GitHub’s token counts only to calculate the token-type split.

​

View Copilot Costs by User in Cost Reports

To start, open a Cost Report, click Filters, select the GitHub provider, and add a Category rule. Choose the Copilot service, select Copilot AI Credits, then click + and add Copilot Cloud Agent. Then set Group By for the view you want: Charges that GitHub does not assign to a user appear as Not tagged with vntg:ai:user_name when you group by vntg:ai:user_name, and as No Resource when you group by Resource.

​

Limits

Vantage keeps organization-level Copilot costs for a day, rather than per-user detail, when:

• Copilot AI-credit charges that day are spread across more than one organization in the enterprise. Per-user detail applies when the GitHub organization connected to Vantage holds your enterprise’s Copilot AI-credit charges.
• More than 1,000 Copilot users were billed in the enterprise that day.
• GitHub has not yet published that day’s Copilot usage metrics. These days gain per-user detail on a later refresh once GitHub publishes them.

​

Disconnect Your Enterprise

To disconnect, open the GitHub integration, select the connection, and click Manage enterprise. You can also select the row labeled Copilot in the GitHub list, or go directly to the GitHub Copilot page. Click Disconnect enterprise. Disconnecting removes the saved connection, and future refreshes return to organization-level Copilot costs. Months that are not re-imported keep their per-user detail, and your GitHub integration and its costs are unaffected. Disconnecting in Vantage does not uninstall the App. To revoke the App’s access in GitHub, an enterprise owner must uninstall the Vantage GitHub Copilot App from the enterprise.

​

Data Refresh

See the provider data refresh documentation for information on when data for each provider refreshes in Vantage. Copilot costs by user refresh with your GitHub costs. Vantage imports the current month daily and re-imports the previous month during the first five days of each month. On each import, Vantage requests per-user billing again for the last three full days and for any day whose enterprise totals changed. After a month closes, Vantage requests per-user billing once more for every day of that month, about four days after month end, to pick up GitHub’s final per-user billing. Per-user detail is added to the GitHub costs Vantage imports after you connect your enterprise, and each person’s GitHub login is set as the Resource on those rows. Months imported before that keep organization-level Copilot costs and a blank Resource. To add per-user detail to earlier months, contact support@vantage.sh to re-import them, as far back as GitHub’s per-person Copilot data reaches.

​

GitHub Reporting Dimensions

On GitHub Cost Reports, you can filter costs across several dimensions:

• Organization (e.g., Organization Name)
• Service (e.g., Actions, Copilot, Packages)
• Category (e.g., Actions, Copilot AI Credits, Copilot Cloud Agent)
• Subcategory (e.g., Actions Linux). With Copilot costs by user, Copilot AI-credit rows use the token type as the subcategory: Input Tokens, Cached Input Tokens, Cache Write Tokens, Output Tokens, or Long Context.
• Resource. For Actions, this is the repository, as organization/repository. With Copilot costs by user, a Copilot AI-credit row uses the person’s GitHub login. Rows with no user, including Copilot seat fees, have no resource.
• Charge Type (e.g., Usage)
• Tags: Includes Virtual Tags created in Vantage for this provider. The following tags are also available for filtering and grouping:
  • owner: The organization name, allowing you to filter and group costs by organization.
  • repo: The repository name when present in the source data, allowing you to filter and group costs by repository.
  • github:user_login: The GitHub login of the person billed for Copilot AI-credit usage. Available with Copilot costs by user.
  • github:cost_center: The GitHub cost center that the Copilot AI-credit usage was billed to on that day, when GitHub reports one. This reflects the cost center at the time of the charge, rather than current membership. Available with Copilot costs by user.

With Copilot costs by user, Vantage also applies Managed AI Tags to Copilot AI Credits and Copilot Cloud Agent costs. This is a normalized vntg:ai: schema shared across all AI providers, so you can analyze AI spend with consistent dimensions. For GitHub Copilot, the following keys are emitted: vntg:ai:model, vntg:ai:raw_model, vntg:ai:model_provider, vntg:ai:token_type, vntg:ai:user_id, and vntg:ai:user_name. vntg:ai:user_name contains the GitHub login, the same value as github:user_login and the row’s Resource, and vntg:ai:user_id is GitHub’s user ID, which stays stable when a user renames their login. vntg:ai:raw_model is set only when the normalized model name differs from GitHub’s label, such as when an Auto: prefix is removed. See Managed AI Tags for the full schema.