docs/content/copilot/get-started/choose-enterprise-plan.md

title, shortTitle, intro, versions, topics, permissions, redirect_from, contentType

title	shortTitle	intro	versions	topics	permissions	redirect_from	contentType
Choosing your enterprise's plan for GitHub Copilot	Choose enterprise plan	Choose between {% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %}.	feature copilot	Copilot	Enterprise owners and billing managers	/copilot/rolling-out-github-copilot-at-scale/choosing-your-enterprises-plan-for-github-copilot /copilot/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot /copilot/tutorials/rolling-out-github-copilot-at-scale/planning-your-rollout/choosing-your-enterprises-plan-for-github-copilot /copilot/get-started/choosing-your-enterprises-plan-for-github-copilot	get-started

When you adopt {% data variables.product.prodname_copilot %} in a company, you will sign up to a {% data variables.product.prodname_copilot_short %} plan designed for businesses. These plans allow you to:

• Choose which users receive access to {% data variables.product.prodname_copilot_short %}
• Meet regulations and security requirements with features like file exclusion, policies, and audit logs
• Benefit from advanced {% data variables.product.prodname_copilot_short %} features

{% data variables.copilot.copilot_enterprise_short %} offers additional features for enterprises that want to customize {% data variables.product.prodname_copilot_short %} for their needs.

This article helps you to decide whether to adopt {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %}.

Sign up for {% data variables.product.prodname_copilot_short %} {% octicon "link-external" height:16 aria-label="link-external" %}

About the plans

{% data variables.product.company_short %} offers two {% data variables.product.prodname_copilot_short %} plans for customers on {% data variables.product.prodname_ghe_cloud %}:

• {% data variables.copilot.copilot_business_short %} ({% data variables.copilot.cfb_price_per_month %} per user per month): includes most {% data variables.product.prodname_copilot_short %} features in IDEs and on the {% data variables.product.github %} website.
• {% data variables.copilot.copilot_enterprise_short %} ({% data variables.copilot.ce_price_per_month %} per user per month): allows companies to customize {% data variables.product.prodname_copilot_short %} for their code and processes, and includes a higher allowance for premium requests. To learn more, see the sections below.

For a full comparison, see our plans page.

About mixed plans

When you subscribe your enterprise account to {% data variables.copilot.copilot_enterprise_short %}, you don't need to use this plan across the whole enterprise. Instead, you can choose a plan individually for each organization in your enterprise. This approach allows you to:

• Evaluate the benefits of {% data variables.copilot.copilot_enterprise_short %} for a smaller group of users before rolling it out further.
• Enable {% data variables.copilot.copilot_enterprise_short %} in the organizations where it will have the most impact, such as organizations with complex documentation or specialized engineering requirements.

What are our goals for {% data variables.product.prodname_copilot_short %}?

To drive and measure downstream impact of {% data variables.product.prodname_copilot_short %}, {% data variables.product.company_short %} recommends leading your rollout with specific engineering goals in mind. Your requirements for {% data variables.product.prodname_copilot_short %} features will depend on your overall goal for the rollout.

For examples of how {% data variables.product.prodname_copilot_short %} can help with common problems in engineering teams, see AUTOTITLE.

Do we have projects with complex requirements?

For complex projects like monorepos or legacy codebases, developers in your company may need to spend a long time finding and reading documentation before they can contribute.

With {% data variables.copilot.copilot_enterprise_short %}, you can create knowledge bases that bring together documentation from one or more repositories in an organization, allowing {% data variables.product.prodname_copilot_short %} to synthesize information from your documentation in its responses.

Will we use {% data variables.copilot.copilot_code-review_short %} at scale?

With {% data variables.copilot.copilot_code-review_short %}, {% data variables.product.prodname_copilot_short %} can provide feedback on pull requests on {% data variables.product.github %}. How much you use this feature depends on the goals of your rollout. For example, if a goal is to increase velocity by accelerating approvals of pull requests, then you may be encouraging developers to use {% data variables.copilot.copilot_code-review_short %} as much as possible.

{% data variables.copilot.copilot_enterprise_short %} includes a higher allowance for premium requests, which are used by {% data variables.copilot.copilot_code-review_short %}. To learn more, see How much will we benefit from premium requests?.

How much will we benefit from premium requests?

Each {% data variables.product.prodname_copilot_short %} plan includes a per-user allowance for premium requests:

• 300 requests per user per month for {% data variables.copilot.copilot_business_short %}
• 1000 requests per user per month for {% data variables.copilot.copilot_enterprise_short %}

By ensuring members have access to enough premium requests, you can drive real business outcomes, such as reducing your backlog with {% data variables.copilot.copilot_coding_agent %}, accelerating pull requests with {% data variables.copilot.copilot_code-review_short %}, or increasing code quality with suggestions from more specialized models.

Regardless of your plan, you can set a spending limit for premium requests over your plan's allowance. Premium requests over the allowance will be charged at a rate of {% data variables.copilot.additional_premium_requests %} per request, with an additional multiplier applied to certain models.

Making a decision

To summarize:

• Choose {% data variables.copilot.copilot_enterprise_short %} if your company has projects with complex requirements or large amounts of documentation. Knowledge bases give {% data variables.product.prodname_copilot_short %} enhanced context, which can save developers time and allow them to focus on tasks they enjoy.
• If you think your developers will benefit from premium models and {% data variables.product.prodname_copilot_short %} code reviews, it may be cost effective to choose {% data variables.copilot.copilot_enterprise_short %} rather than pay for premium requests over your allowance.
• If you're not sure about a full rollout, choose {% data variables.copilot.copilot_enterprise_short %} at the enterprise level and enable it for individual organizations where it will have the most impact.
• Make your decision based on your downstream goals for the {% data variables.product.prodname_copilot_short %} rollout.

Further reading

• AUTOTITLE
• AUTOTITLE