About per-user pricing
The foundation of your bill is the number of standard licensed seats that you choose for your enterprise.
GitHub uses a unique-user licensing model. For enterprise products that include multiple deployment options, GitHub determines how many licensed seats you're consuming based on the number of unique users across all your deployments.
Each user only consumes one license, no matter how many GitHub Enterprise Server instances the user uses, or how many organizations the user is a member of on GitHub Enterprise Cloud. This model allows each person to use multiple GitHub Enterprise deployments without incurring extra costs.
To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your GitHub Enterprise Server and GitHub Enterprise Cloud environments. For more information, see "About licenses for GitHub Enterprise."
In addition to licensed seats, your bill may include other charges, such as GitHub Advanced Security. For more information, see "About billing for your enterprise."
People that consume a license
GitHub bills for the following accounts for each deployment of GitHub Enterprise.
Accounts that consume a license on GitHub Enterprise Cloud
GitHub bills for each of the following accounts on GitHub Enterprise Cloud:
- Enterprise owners who are a member or owner of at least one organization in the enterprise
- Organization members, including owners
- Outside collaborators on private or internal repositories owned by your organization, excluding forks
- Dormant users who are a member or owner of at least one organization in the enterprise
If your enterprise does not use Enterprise Managed Users, you will also be billed for each of the following accounts:
- Anyone with a pending invitation to become an organization owner or member
- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
Notes:
- GitHub counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
- If an invitee does not accept the invitation within seven days, the pending invitation expires automatically.
GitHub does not bill for any of the following accounts:
- Managed user accounts that are suspended
- Enterprise owners who are not a member or owner of at least one organization in the enterprise
- Enterprise billing managers
- Billing managers for individual organizations
- Anyone with a pending invitation to become a billing manager
- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
- Guest collaborators who are not organization members (see "Roles in an enterprise")
- Users of Visual Studio subscriptions with GitHub Enterprise whose accounts on GitHub.com are not linked, and who do not meet any of the other criteria for per-user pricing
- Users who have been provisioned with a managed user account, but are not members of any organizations in the enterprise
Accounts that consume a license on GitHub Enterprise Server
After a user successfully authenticates to a GitHub Enterprise Server instance for the first time, the user consumes a seat.
Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "Suspending and unsuspending users."
Dormant users do occupy a seat license. Administrators can suspend dormant users to free licenses. For more information, see "Managing dormant users."
About changes to your subscription
You can add more licensed seats to your enterprise at any time. If you pay for more seats than are being used, you can also reduce the number of seats.
If you use an enterprise account on GitHub.com and have questions about changes to your subscription, contact GitHub's Sales team.