Skip to main content
ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。

About billing for your enterprise

You can view billing information for your enterprise account on GitHub.com.

About billing for your enterprise

GitHub bills monthly for the total number of members in your enterprise account, as well as any additional services you use with GitHub Enterprise Cloud.

For GitHub Enterprise Cloud customers with an enterprise account, GitHub bills through your enterprise account on GitHub.com. For invoiced customers, each invoice includes a single bill charge for all of your paid GitHub.com services and any GitHub Enterprise Server instances. For more information about usage and invoices, see the following.

Administrators for your enterprise account on GitHub.com can access and manage billing for the enterprise. For more information, see "Roles in an enterprise."

If you purchased GitHub Enterprise through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for any Codespaces usage, and for GitHub Actions or GitHub Packages usage beyond the amounts included with your account. For more information, see "Connecting an Azure subscription to your enterprise."

Per-user pricing

GitHub bills for services consumed on GitHub.com, each user for deployments of GitHub Enterprise Server, and each member of organizations on GitHub Enterprise Cloud. For more information about per-user pricing, see "About per-user pricing."

With per-user pricing, each person consumes one license. GitHub identifies individuals by primary email address.

GitHub bills for the following people.

  • 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
  • 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
  • Each user on any GitHub Enterprise Server instance that you deploy

GitHub does not bill for any of the following people.

  • Enterprise owners who are not a member or owner of at least one organization in the enterprise
  • Enterprise billing managers
  • Organization billing managers for individual organizations on GitHub Enterprise Cloud
  • Anyone with a pending invitation to become an enterprise or organization billing manager
  • Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization

注釈: If an invitee does not accept the invitation within seven days, the pending invitation expires automatically. After expiration, GitHub will no longer bill you for the pending invitation. If a SCIM request from your identity provider (IdP) generates the invitation, the invitation will not expire.

For more information about roles, see "Roles in an enterprise" or "Roles in an organization."

For more information about outside collaborators, see "Adding outside collaborators to repositories in your organization."

About synchronization of license usage

GitHub Enterprise offers two deployment options. In addition to GitHub Enterprise Cloud, you can use GitHub Enterprise Server to host development work for your enterprise in your data center or a supported cloud. For more information, see "GitHub's products."

GitHub Enterprise uses a unique-user licensing model, where each person only consumes one license, no matter how many GitHub Enterprise Server instances the person uses, or how many organizations the person is a member of on GitHub Enterprise Cloud. This model allows each person to use multiple GitHub Enterprise environments without incurring extra costs.

For a person using multiple GitHub Enterprise environments to only consume a single license, you must synchronize license usage between environments. Then, GitHub will deduplicate users based on the email addresses associated with their personal accounts. Multiple personal accounts will consume a single license when there is a match between an account's primary email address on GitHub Enterprise Server and/or an account's verified email address on GitHub.com. For more information about verification of email addresses on GitHub.com, see "Verifying your email address."

When you synchronize license usage, only the user ID and email addresses for each personal account on GitHub Enterprise Server are transmitted to GitHub Enterprise Cloud. For more information, see "Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud" in the GitHub Enterprise Server documentation.

Further reading