GitHub Products, Features, and Licensing: A 2026 Overview

Why I Wrote This Article

When people hear “GitHub,” they probably think first of repositories for storing source code, followed by coding assistance from GitHub Copilot.

I use both regularly. But when I took another look at GitHub’s feature list, I was reminded that GitHub is much more than a service that makes writing code easier.

The platform connects the software development lifecycle in one place: planning with Issues and Projects, reviews through Pull Requests, automation with Actions, security controls such as Code Security and Secret Protection, and governance through SSO, audit logs, and rulesets.

Used together, these capabilities let organizations build a development platform that can:

• Trace requirements and tasks through code changes, reviews, and releases
• Maintain quality through rules and automation instead of relying solely on manual checks
• Integrate security checks into everyday workflows without slowing developers down
• Centrally manage access, policies, and usage across the organization

Looking beyond repositories and Copilot reveals GitHub as an integrated platform for delivering projects securely under effective governance. This article presents that broader picture by organizing GitHub’s products, plans, pricing, and purchasing options.

Table of Contents

• The Difference Between Features and Products
• 1. GitHub Plans: The Foundation for Code, Projects, and Governance
• 2. GitHub Copilot: Bringing AI into the Development Workflow
• 3. GitHub Actions: Automating CI/CD and Business Processes
• 4. GitHub Codespaces: Standardized Cloud Development Environments
• 5. GitHub Packages: Managing Packages Alongside Code
• 6. GitHub Advanced Security and Code Quality: Building Checks into Development
• 7. Free Clients and Integration Features
• 8. How to Purchase GitHub Products
• 9. Choosing Products for Enterprise Adoption
• Summary
• Official Sources

The Difference Between Features and Products

GitHub’s feature list contains many names, but not every item is purchased separately.

• Features included with a core GitHub plan: Repositories, Pull Requests, Issues, Projects, Discussions, wikis, organizations, auditing, permission management, and more
• Products licensed separately from the core platform: GitHub Copilot, GitHub Code Security, GitHub Secret Protection, and GitHub Code Quality
• Usage-based products: GitHub Actions, GitHub Codespaces, GitHub Packages, and others
• Free clients and related capabilities: GitHub Desktop, GitHub CLI, GitHub Mobile, APIs, webhooks, and more

In practice, you first choose a core GitHub plan, add AI or security products as needed, and then manage usage for CI/CD and development environments.

1. GitHub Plans: The Foundation for Code, Projects, and Governance

GitHub’s core platform is not only for repository management. It is also the hub for collaborative development and project management.

Projects and Issues are included in GitHub plans; they are not separate paid products. The extent of the available functionality depends on the plan.

Plans and Pricing

For a detailed comparison of Team and Enterprise, see the official GitHub plans documentation and the GitHub Pricing feature comparison. In addition to Team features, Enterprise provides SAML SSO, SCIM, audit log streaming, and policy and billing management across multiple organizations.

For enterprises, the important questions are not simply how many features a plan includes, but who can access the platform, which rules can be enforced, and what can be audited later. Enterprise is the primary option when identities, policies, and billing must be managed across multiple organizations.

GitHub Enterprise has two deployment options: Enterprise Cloud, hosted by GitHub, and Enterprise Server, operated in your own environment. Features and billing differ, so organizations should decide between cloud hosting and self-hosting before procurement.

2. GitHub Copilot: Bringing AI into the Development Workflow

GitHub Copilot is more than a code-completion product. Through IDE and GitHub chat experiences, agents, code review, and the CLI, it supports implementation, research, and review across the development workflow.

Individual Plans

Organization and Enterprise Plans

Each plan includes an allowance of GitHub AI Credits, and usage beyond that allowance is billed on a metered basis. The official Pricing Calculator lists $0.04/request as a reference unit price for overage requests.

For enterprise use, centrally managing seat assignment, usage policies, and auditing with Business or Enterprise is generally more appropriate than having each individual purchase Pro.

Since April 22, 2026, new self-service sign-ups for Copilot Business have been temporarily suspended for organizations on GitHub Free and Team. For a new deployment, check the latest official guidance or contact GitHub Sales.

3. GitHub Actions: Automating CI/CD and Business Processes

GitHub Actions automates not only builds, tests, and deployments, but also processes such as labeling Issues, handling approvals, running scheduled jobs, and performing security checks.

Rather than being sold as a separate monthly license, Actions combines a usage allowance included with each GitHub plan with metered charges for additional runtime and storage.

Standard GitHub-hosted runners for public repositories and self-hosted runners are free to use. Larger runners are not covered by the included allowance.

Rates vary by operating system, CPU, GPU, and larger-runner configuration. For a reliable production estimate, use the GitHub Pricing Calculator.

4. GitHub Codespaces: Standardized Cloud Development Environments

GitHub Codespaces launches a preconfigured development environment in the cloud from a repository. Managing a devcontainer as code reduces differences among developer environments and shortens onboarding time.

Organization and Enterprise plans do not include a free allowance; compute and retained storage are billed based on usage.

Compute charges stop while a codespace is stopped, but storage charges continue for as long as the codespace or a prebuild is retained. Organizations should define controls for eligible users, machine types, and budgets.

5. GitHub Packages: Managing Packages Alongside Code

GitHub Packages manages npm, NuGet, Maven, RubyGems, and other packages in connection with repository permissions. Public packages are free. Private usage becomes metered after it exceeds the allowance included with the GitHub plan.

When GitHub Actions downloads a package using GITHUB_TOKEN, the transfer does not count toward the data-transfer allowance. GitHub also currently states that image storage and bandwidth for the Container registry are free.

6. GitHub Advanced Security and Code Quality: Building Checks into Development

The paid capabilities of GitHub Advanced Security are now available as two products: GitHub Code Security and GitHub Secret Protection. Public repositories can use code scanning, secret scanning, and some dependency-review features for free, while advanced capabilities for private repositories require licenses.

GitHub Code Security

CodeQL code scanning, Copilot Autofix, dependency review, advanced Dependabot capabilities, and Security Campaigns help teams find and remediate vulnerabilities before code is merged.

GitHub Secret Protection

Secret scanning, push protection, custom patterns, and AI-based generic secret detection help find and prevent the exposure of tokens and passwords.

Here, an active committer is a unique user who pushed a commit to an eligible repository within the previous 90 days. If the same person contributes to multiple eligible repositories, that person is counted once across the organization or enterprise.

Payment options include metered billing, under which the number of licenses actually used is billed monthly, and volume/subscription agreements for enterprise customers, which typically commit to a fixed quantity for at least one year.

GitHub Code Quality (Generally Available in July 2026)

After this article was published, GitHub announced the general availability of GitHub Code Quality on July 21, 2026; the GitHub Changelog entry is dated July 20.

GitHub Code Quality combines deterministic CodeQL analysis with AI-assisted detection to identify maintainability and reliability issues in Pull Requests. Copilot Autofix proposes remediations that developers can review and apply before merging.

At general availability, the product includes:

• Organization-wide enablement and a dashboard showing maintainability and reliability scores across repositories
• Code-coverage results in Pull Requests based on existing test reports in Cobertura XML format
• Quality gates and coverage thresholds integrated with GitHub rulesets, including an evaluate mode for phased adoption
• An API for enabling the product on repositories and retrieving results

GitHub Code Quality is available for GitHub Enterprise Cloud and GitHub Team. At general availability, it does not support GitHub Enterprise Server. It is not bundled with GitHub Advanced Security; it is a separate paid product that complements it.

For Code Quality, an active committer is a user who pushed a commit within the previous 90 days to a repository where the product is enabled. A person who contributes to multiple repositories in the same organization is counted once, and bot accounts are not billed. The AI capabilities do not require a GitHub Copilot subscription.

Organizations that used the Public Preview do not need to migrate or reconfigure the product, but billing began when it became generally available. To avoid unintended charges, review where Code Quality is enabled at both the organization and repository levels.

7. Free Clients and Integration Features

These capabilities operate according to the permissions of the GitHub account and target repository. Paid Marketplace applications and charges from connected cloud services are billed separately.

8. How to Purchase GitHub Products

There are three main purchasing paths. The right choice depends not only on contract size, but also on where billing should be consolidated and whether license counts should be fixed or reconciled against actual usage.

A. Self-Service Purchase on GitHub.com

You can register a payment card or PayPal account and make purchases under GitHub’s Billing & licensing settings.

• Suitable for getting started quickly with GitHub Team or an individual Copilot plan
• Supports metered billing for Actions, Codespaces, Packages, and other products
• Allows products that offer both options to be switched between monthly and annual billing on GitHub
• Provides budgets and alerts for controlling unexpected usage charges

This is the easiest path for a small deployment or proof of concept. Organizations that require internal procurement procedures, invoicing, or negotiated contract terms should consider a sales agreement instead.

B. Volume Purchase Through GitHub Sales

Contact GitHub Sales for a quote and contract covering Enterprise or add-on products.

• Company-wide adoption of GitHub Enterprise or Copilot Business/Enterprise
• Volume licenses for Code Security and Secret Protection
• Agreements that include GitHub Enterprise Server
• Annual contracts, invoice billing, legal and security reviews, and negotiated support terms

Volume/subscription agreements for Advanced Security typically require the purchase of a fixed number of licenses for at least one year. Additional licenses must be purchased if usage exceeds the contracted quantity. For a large deployment, consult GitHub or Microsoft Sales, or a licensing partner, to confirm whether the purchase can be made under your organization’s enterprise agreement.

C. Consolidating Metered Charges in an Azure Subscription

Connecting an Azure subscription to a GitHub organization or enterprise account lets you pay for GitHub metered services through Azure.

Common eligible charges include usage for Actions, Codespaces, Packages, additional Copilot consumption, and metered Advanced Security licenses. This option suits organizations that want to review GitHub charges alongside other cloud spending in Azure Cost Management.

The connection requires the following permissions:

• GitHub: Owner of the target organization or enterprise
• Azure: Owner of the target subscription
• Microsoft Entra ID: Tenant-wide administrator consent or an administrator consent workflow

Connect the Azure Subscription ID under Billing & licensing > Payment information > Metered billing via Azure in GitHub.

Connecting Azure primarily changes the payment destination for metered charges. Existing volume, subscription, or prepaid Enterprise licenses continue to be billed under their current arrangements until the contract expires or transition guidance is provided. Simply connecting a subscription does not convert an annual GitHub license to Azure pay-as-you-go billing.

9. Choosing Products for Enterprise Adoption

Rather than evaluating each product in isolation, select the capabilities needed across the delivery lifecycle: planning (Issues/Projects) → implementation (repositories/Copilot/Codespaces) → review (Pull Requests) → inspection (Code Security/Secret Protection) → release (Actions/Packages) → governance (Enterprise). This makes both the adoption goals and their costs easier to understand.

Summary

GitHub is more than repositories plus Copilot. It can connect project management, collaborative review, CI/CD, development environments, package management, security, identity, and auditing in a single development workflow.

Its pricing model is easiest to understand in three layers:

1. GitHub plans: Per-user licenses for Free, Team, or Enterprise
2. Add-on products: Seat-based or committer-based licenses for Copilot, Code Security, Secret Protection, and Code Quality
3. Usage-based charges: Metered usage for Actions, Codespaces, Packages, AI Credits, and other services

Purchasing options include self-service on GitHub.com, volume agreements through GitHub Sales, and consolidation of metered charges in an Azure subscription. Start by defining your development process and governance requirements, then combine the core plan and add-on products that meet them.

Official Sources

• GitHub features
• GitHub Pricing
• GitHub Pricing Calculator
• GitHub Copilot plans
• Billing for GitHub Actions
• Billing for GitHub Codespaces
• Billing for GitHub Packages
• Billing for GitHub Advanced Security
• GitHub Code Quality is generally available
• About GitHub Code Quality
• Billing for GitHub Code Quality
• Connecting an Azure subscription
• Managing GitHub payment information