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

このバージョンの GitHub Enterprise はこの日付をもって終了となりました: 2022-06-03. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてく� さい。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してく� さい。

About licenses for GitHub Enterprise

You can synchronize your license usage between GitHub Enterprise deployments, and use a license file to unlock each GitHub Enterprise Server instance.

About licensing for GitHub Enterprise

GitHub Enterprise offers two deployment options. In addition to GitHub Enterprise Server, you can use GitHub Enterprise Cloud to host development work for your enterprise on GitHub.com. For more information, see "GitHub's products."

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 account only consumes one license, no matter how many GitHub Enterprise Server instances the user account uses, or how many organizations the user account 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 deployments.

In order to use a GitHub Enterprise Server instance, you must upload a license file that GitHub provides when you purchase, renew, or add user licenses to GitHub Enterprise.

About synchronization of license usage for GitHub Enterprise

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 user accounts. Multiple user 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" in the GitHub Enterprise Cloud documentation.

When you synchronize license usage, only the user ID and email addresses for each user 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."

About license files for GitHub Enterprise

When you purchase or renew GitHub Enterprise, GitHub provides a license file for GitHub Enterprise Server インスタンス. A license file has an expiration date and controls the number of people who can use GitHub Enterprise Server インスタンス. After you download and install GitHub Enterprise Server, you must upload the license file to unlock the application for you to use.

For more information about downloading your license file, see "Downloading your license for GitHub Enterprise."

For more information about uploading your license file, see "Uploading a new license to GitHub Enterprise Server."

If your license expires, you won't be able to access GitHub Enterprise Server via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see "Configuring backups on your appliance."

If you have any questions about renewing your license, contact GitHubの営業チー� .

Further reading