Skip to main content
Licensing can feel academic—until you get a surprise invoice for tens or hundreds of thousands of dollars. This guide explains GitHub Enterprise billing in practical terms so you can forecast and control costs. GitHub Enterprise billing breaks down into three independent mechanisms. A useful analogy is a family mobile phone plan: you pay for lines (seats), extra for heavy data users (Advanced Security committers), and share a limited monthly data pool (Actions minutes). Quick summary table Useful references:

1) Seat licenses

  • Seats are billed per human user, not per organization.
  • If Jane is a member of three organizations, she still counts as one billable seat.
  • In practice: if you have 2,000 distinct engineers across 10 organizations, GitHub bills for 2,000 seats — not 20,000.
This behavior benefits organizations that rely on central identity providers and people who operate across multiple orgs.

2) GitHub Advanced Security (GSAS)

  • Advanced Security billing is focused on activity: it’s billed per active committer on private repositories with GSAS enabled.
  • “Active committer” = a human (or account) that makes at least one commit in the billing window.
  • GSAS uses a 90-day trailing window, so commit activity can affect billing for up to three months after the last commit.
A slide titled "Advanced Security – The Data Add-On" showing a purple "Advanced Security" badge with the note "billed per active committer" and a row of user icons, two of which are highlighted in blue while the others are grey and labeled "no commits."
Important: GSAS charges are activity-based. Contractors or temporary contributors who commit even once can continue to count toward billing for up to 90 days after their last commit. Incorporate this trailing window into offboarding and cost forecasts.

3) GitHub Actions minutes

  • Actions minutes are a shared pool per account/org with an included allotment and overage rates.
  • Runners consume minutes differently: macOS runners are billed at 10× the rate of Ubuntu/Linux runners. That multiplier makes macOS builds much more expensive.
  • Forecasting Actions spend requires knowing: number of developers, pushes per day, average build minutes, and runner type.

A seat-license insight many new admins miss: GitHub counts unique human beings across organizations. If you have 2,000 engineers spread across 10 organizations, GitHub bills 2,000 seats — not 20,000.
An infographic titled "GitHub Counts Unique Humans" showing 2,000 engineers spread across 10 organizations and explaining that GitHub bills 2,000 seats (not 20,000). It notes that a developer who appears in multiple organizations still counts as a single seat.
What does not work in your favor: bots. If a CI bot or service account commits to repositories, that account may be counted as a paid seat and may also consume an Advanced Security committer license. Options to reduce cost impact:
  • Use machine identities that do not require full user seats where possible.
  • Centralize bot activity under fewer accounts.
  • Avoid committing from many separate bot accounts.
Another important detail: GitHub Advanced Security uses a 90-day trailing window. If a contractor commits in January and leaves in February, they will still be included in Advanced Security billing through April. Plan offboarding and budgets accordingly.
A slide titled "The 90-Day Trailing Window" showing month boxes for Jan–Apr where Jan is labeled "commits" (blue person icon) and Feb shows a grey person with a red strike-through labeled "leaves." A purple pill reading "Still billed" appears beneath the months.

Example: Actions minute multiplier math

Run the numbers explicitly so you can forecast and justify spend. Scenario:
  • Team: iOS team (macOS runners)
  • Developers: 15
  • Pushes per developer: 6 per day
  • Build time per push: 25 minutes (macOS)
Step-by-step calculation:
This calculation is for a single team. Multiply across teams and runner types to build a reliable monthly forecast. Cost multipliers reference (example)
Remember these three operational facts:
  • macOS GitHub-hosted runners count as 10× a Linux/Ubuntu runner for billing.
  • GitHub Advanced Security is billed per active committer on private repositories and uses a 90-day trailing window.
  • One human appearing in multiple organizations counts as a single seat.

Watch Video