The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →GitHub’s enhanced billing platform did not turn GitHub Free for organizations into a paid plan. It replaced the older, simpler billing controls with a more detailed system for viewing usage, setting budgets, receiving alerts, and downloading reports. The rollout began for new Free organizations on February 4, 2025, was announced on February 19, 2025, and has since become GitHub’s standard billing experience.
The important qualification is that “Free” does not mean every GitHub service is unlimited or incapable of generating charges. Actions, Packages, Git LFS, and other metered services have product-specific allowances and overage rules.
As an Amazon Associate I earn from qualifying purchases.
What GitHub announced
GitHub announced the enhanced billing platform on February 19, 2025. New organizations on the GitHub Free plan began receiving it on February 4, while existing Free organizations were scheduled for migration over the following months. GitHub said affected organizations would receive advance notice by email and an in-product banner.
The announcement described a migration from the former spending limits setting to the modern budgets system. The change was more than a cosmetic redesign: administrators gained more detailed usage views, configurable alerts, downloadable reports, and additional controls over eligible metered products.
Current GitHub documentation says the enhanced billing platform is now available to all users. The 2025 rollout should therefore be understood as a completed migration, not as a new 2026 feature. See GitHub’s original announcement and its current billing guidance.
#1 Best Overall
What the enhanced platform adds
The platform centralizes billing and usage management for organizations. Depending on the products and permissions involved, administrators can see:
- Metered usage by organization, repository, product, or SKU
- Current usage over selected time periods
- Gross usage, billable usage, units, and pricing information
- Budgets and budget-threshold alerts
- Alerts as included allowances approach depletion
- CSV usage reports
- Promotions, discounts, and certain licensing-related information
- Summarized billing data through a REST API
That makes the platform useful for more than checking an invoice. It can help an organization identify which repository is consuming Actions minutes, determine whether Git LFS bandwidth is being exhausted, allocate costs, and decide whether the Free plan remains adequate.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhere to find billing and usage
For an organization, the main navigation path is:
- Open GitHub and go to Organizations.
- Select the organization.
- Open Settings.
- Select Billing & Licensing.
- Choose Overview, Usage, or Budgets and alerts.
Under Usage, select Metered usage or, where applicable, AI usage. You can filter by repository, product, SKU, group, and time period. Available periods can include the current hour, today, this month, last month, this year, last year, and custom date ranges.
Expand rows or dates to inspect units, price per unit, and actual usage. To obtain a downloadable report, use Get usage report. GitHub’s detailed usage report is primarily a web-interface feature; the REST usage endpoint provides summarized billing information and should not be treated as an exact replacement for every field in the dashboard or CSV export. See GitHub’s usage-insights guide.
Who can access the information?
Organization owners generally have the broadest organization-level billing access. They can view metered and repository usage, create organization and repository budgets, download CSV reports, and view available promotions, discounts, and certain licensing information.
Organization billing managers can view organization metered usage, view organization-level budgets, and download CSV reports. Depending on their current role permissions, billing managers may also handle payment methods, receipts, plan changes, billing managers, and sponsorship-related billing tasks.
An ordinary organization member should not be assumed to have access to billing data simply because they can access repositories. GitHub’s billing-roles documentation is the authority for the current permission split.
Does GitHub Free for organizations allow paid overages?
It can. The Free plan includes allowances for several metered products, but the result after an allowance is depleted depends on the product, the organization’s budget configuration, and whether payment or overage billing is available.
Some eligible metered products can be stopped when a budget is exhausted. Other products, particularly many license-based products, may use budgets for notification without treating them as a universal hard spending cap. Consequently, neither of these statements is safe:
- “We use GitHub Free, so we can never be charged.”
- “A $0 budget automatically blocks every possible GitHub charge.”
Review each product’s billing behavior, then configure budgets at the scope that matches the risk. A payment method, an active budget, and a product’s specific overage rules can materially affect the outcome.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Current Free-plan allowances
GitHub’s current included-usage table lists the following allowances for GitHub Free for organizations:
| Product | Included usage |
|---|---|
| GitHub Actions minutes | 2,000 minutes per month |
| GitHub Actions storage | 500 MB |
| GitHub Packages storage | 500 MB |
| GitHub Packages data transfer | 1 GB per month |
| Git LFS storage | 10 GB |
| Git LFS bandwidth | 10 GB |
| GitHub Codespaces | No allowance listed for Free organizations |
These figures reflect GitHub documentation checked on August 18, 2026. They are not permanent guarantees; GitHub can change plan allowances and usage-based billing rules. Check the current included-usage table before making a budgeting or plan decision.
How budgets and alerts work
To create a budget, go to:
Organization → Settings → Billing & Licensing → Budgets and alerts → New budget
Depending on the product, you can choose a product-level budget, SKU-level budget, or bundled AI-credits budget. Select the scope, enter the amount, choose alert thresholds, and—if GitHub supports it for that product—enable the option to stop usage when the budget is exhausted.
Budget scopes can include the whole organization or an individual repository. Enterprise billing can provide additional scopes such as organizations, repositories, and cost centers.
GitHub documents budget alerts at configured percentages such as 75%, 90%, and 100%. Separate included-usage alerts can notify administrators at milestones such as 90% and 100% of an allowance. A budget alert is a warning unless the relevant product supports usage stopping and that option has been enabled.
Budgets are also not retroactive. A budget created today does not control usage that occurred earlier in the month or before the budget existed. It is therefore better to configure budgets before a workload is deployed, not after an unexpected usage spike.
Git LFS: the separate billing change
Git LFS deserves special attention because the announcement also covered its move from prepaid, quota-based data packs to usage-based metered billing. Unused prepaid balances were to be converted into credits.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
GitHub Free for organizations currently includes 10 GB of Git LFS storage and 10 GB of bandwidth. These measure different things:
- Storage reflects LFS objects associated with the repository. It is not simply the volume uploaded during the current month. Objects can continue contributing to storage after the month in which they were uploaded.
- Bandwidth is consumed when LFS objects are downloaded, including through development workflows, continuous integration, forks, or other repeated retrievals.
Under GitHub’s documented behavior, setting the relevant budget to $0 can block Git LFS over-quota use for the rest of the calendar month rather than charging for it. If the budget is deleted, GitHub says there is no spending limit and usage beyond the included quota is billed. The repository owner is responsible for the relevant Git LFS billing relationship.
Do not assume that a repository with little new upload activity has little LFS exposure. Large historical objects and frequent CI or fork downloads can affect storage and bandwidth separately. See GitHub’s Git LFS billing documentation.
CSV reports and API automation
The web dashboard is the best option when an administrator needs detailed filtering by repository, product, SKU, and date. The CSV report is useful for finance reconciliation, internal chargebacks, or a periodic review outside GitHub.
Recommended Free Tools
Organizations can also use GitHub’s billing-usage REST endpoint for recurring summaries and internal dashboards. The requester must have the required organization administration permissions. The API is useful for automation, but GitHub distinguishes its summarized billing data from the more detailed usage information available in the web interface.
Use the billing-usage API documentation to verify the current endpoint, authorization requirements, and response fields before building an integration.
Reporting limitations and delays
- Usage graphs are organized around calendar-month boundaries and may not match an organization’s preferred internal accounting period.
- Certain security-product changes can take up to two hours to appear in usage data.
- After migration, some historical usage may not appear visually in the new dashboard. GitHub’s announcement indicated that a pre-transition usage report could be downloaded; this should not be described as historical data being erased.
- A newly created budget does not control earlier usage.
These limitations matter when reconciling GitHub’s dashboard with an internal finance system. A recent change that is missing from the graph may reflect reporting delay rather than incorrect billing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common mistakes to avoid
Assuming Free means no overages
Free organizations can still consume metered services beyond included allowances. Check the product table and the organization’s current budget behavior.
Treating every budget as a hard cap
Some metered products can be stopped at a budget threshold; many license-based products use budgets primarily for alerts. A $0 budget is not a universal guarantee against every charge.
Monitoring only the organization total
A repository-level budget or usage filter can reveal which project is responsible for a spike. Organization-wide totals alone may hide a single repository’s Actions, Packages, or LFS activity.
Best Value
Confusing included-usage alerts with dollar budgets
An alert that an allowance is nearly depleted is not necessarily the same as a budget alert or a usage block. Review both the product allowance and the configured dollar or usage threshold.
Assuming recent activity appears immediately
Some usage data is delayed, particularly for certain security products. Allow for the documented delay before escalating a discrepancy.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Measuring LFS only by monthly uploads
LFS storage can reflect all associated objects, while bandwidth reflects downloads. Upload volume alone does not describe total LFS exposure.
Should a Free organization upgrade?
The enhanced billing platform does not by itself make an upgrade necessary. Start by reviewing actual usage, then consider:
- Whether Actions, Packages, or LFS usage regularly exceeds Free allowances
- Whether workloads are predictable enough to manage with product-specific budgets
- Whether the organization needs repository-level controls or automated reporting
- Whether a paid plan provides collaboration, governance, or administrative features the team needs
- Whether enterprise-wide reporting, cost centers, and centralized oversight justify GitHub Enterprise Cloud
GitHub Free may remain appropriate for small teams and open-source organizations whose usage fits within the included quotas. GitHub Team may be more suitable when a paid collaboration plan or larger included allowances are needed. Enterprise Cloud is aimed at organizations requiring broader administration, governance, centralized billing, and enterprise reporting.
For current pricing and plan packaging, use GitHub’s official pricing page rather than relying on an older quoted price. GitHub can change prices, allowances, and metered rates.
Bottom line
The enhanced billing platform is primarily a migration to better billing visibility and control—not a conversion of GitHub Free into a paid plan. It gives organization owners and billing managers detailed usage views, budgets, alerts, reports, and API access. But Free organizations still need to understand each metered product’s included allowance and overage behavior, particularly for GitHub Actions, Packages, and Git LFS.
The practical approach is to inspect usage, set budgets at the right organization or repository scope, make sure alerts reach the people monitoring spend, and upgrade only when quotas, governance, or collaboration requirements justify it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
