Why This Matters

Choosing the wrong plan costs money in two directions: too small and you hit rate limits at the worst possible moment (mid-debugging session, mid-PR); too large and you pay for credits you'll never burn. The April 2026 transition to usage-based billing made the math more nuanced — base plan prices stayed the same, but every interaction now draws from a credit allowance that varies by model and operation. This lesson gives you the framework to pick once and pick right.

Concept Explained

GitHub Copilot is sold on six tiers, four for individuals and two for organizations. All prices below are current as of August 2026 and reflect the post-April-2026 usage-based billing model. Always verify at github.com/features/copilot/plans before subscribing — prices can change.

How It Works

Since April 2026, every Copilot plan comes with a base allowance of AI credits per month. Different operations consume different amounts of credits:

• Inline completions: small credit cost per suggestion.
• Chat messages: medium cost, varies by model (GPT-5 mini is cheapest; GPT-5 highest; Claude and Gemini somewhere in between).
• Coding-agent sessions: largest cost — each session consumes many credits.
• Multi-model selections (Claude, Gemini) typically cost more credits than the default.

When you exhaust your monthly credit allowance, you can either wait for the next cycle, upgrade, or buy top-up credits. The transition preserved base plan pricing: Pro stayed at $10/month, Pro+ at $39/month, Business at $19/user/month, Enterprise at $39/user/month.

Step-by-Step Tutorial

1. Survey the six plans

The current six tiers (verified August 2026) are:

• Free — $0. Limited monthly completions and chat messages. No multi-model, no Spaces, no coding agent. Good for trying Copilot out.
• Pro — $10/month. ~1,000 base AI credits. Inline completions, Chat, slash commands, CLI, GitHub.com chat, coding agent. Multi-model selection. The default for individual developers.
• Pro+ — $39/month. ~3,900 base AI credits. Higher allowances, priority access during peak times, access to premium models.
• Max — $100/month (some sources cite $200; verify on the plans page). ~10,000 base AI credits. For power users who run the coding agent heavily.
• Business — $19/user/month. Per-seat org management, organization policy, training-data opt-out at the org level, content filter enforcement, REST API access for metrics and seat management. Customer data not used for training.
• Enterprise — $39/user/month. Everything in Business plus enterprise-grade security, audit log export, enterprise-wide policy, and deeper GitHub integration.

2. Match plan to reader profile

Three common profiles and their best fit:

• Student or hobbyist → Free. Upgrade to Pro only if you hit limits regularly (more than ~3 hours/day of active Copilot use).
• Individual professional developer → Pro. Move to Pro+ only if you use the coding agent daily or hit credit walls mid-month.
• Team of 5–50 developers → Business. The per-seat price is barely above Pro, and you get org policy, training opt-out, and the REST API for seat management.

If you have a strict compliance regime (finance, healthcare, government), Enterprise is usually required for the audit log export and enterprise policy controls.

3. Estimate monthly cost for a team

For a 10-person team on Business: 10 × $19 = $190/month base. Add top-up credits only if the team uses the coding agent heavily — a typical dev burns 1,000–3,000 credits/month; the coding agent can burn 500+ per session. Budget an extra 20% for top-ups if your team delegates more than 5 issues/week to the agent.

4. Verify before subscribing

Prices and credit allowances change. Always verify at github.com/features/copilot/plans and at the official billing docs before committing.

Real-World Example

A 20-person startup adopted Copilot Business in early 2026 at $19/user/month = $380/month. In their first month, the team collectively burned through their included credits by week three, mostly from the coding agent. Rather than upgrading everyone to Enterprise, they bought $200 of top-up credits and adopted a simple rule: "use the coding agent only for issues tagged agent-ok". The next month's bill dropped to $420 total — predictable, controlled, and 35% cheaper than going Enterprise.

Example Prompts / Commands / Code

Profile                          | Plan         | Why
---------------------------------|--------------|----------------
Student learning weekends        | Free         | Limits are fine; save money
Solo indie dev (daily use)       | Pro          | 1,000 credits is enough
Heavy agent user (solo)          | Pro+ or Max  | Agent sessions cost more
5-person team, no compliance     | Business     | Per-seat, REST API, no training
50-person regulated company      | Enterprise   | Audit, policy, indemnification

Operation                 | Approx credits
--------------------------|----------------
Inline completion         | ~1
Chat message (GPT-5 mini) | ~5
Chat message (GPT-5)      | ~15
Coding agent session      | ~300–800
Extension call             | varies

Common Mistakes

• Picking Pro+ or Max because “more is better” — most users never need them.
• Forgetting that Business and Enterprise prices are per user, not per org.
• Assuming your existing GitHub Teams subscription includes Copilot — it doesn't; Copilot is a separate add-on.
• Buying top-up credits reactively instead of budgeting upfront — emergency top-ups feel worse than planned ones.
• Mixing personal Pro accounts with Business seats in the same org — pick one or the other per team.
• Ignoring the training-data opt-out: Free and Pro may use your data for training unless you opt out (Business/Enterprise do not). See BE-34.

Best Practices

• Start one tier below your gut instinct. You can always upgrade; downgrading is harder.
• Track credit burn for one month before deciding to upgrade. Use the Copilot usage page in your GitHub settings.
• If you delegate to the coding agent more than 5 times/week, you probably need Pro+ or higher.
• For teams, prefer Business over individual Pro accounts — policy, audit, and seat management pay off quickly.
• Review your plan quarterly. Copilot pricing has changed multiple times in 18 months.
• Document why you chose your plan. When finance asks “can we cut this?”, you'll have a justification ready.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• GitHub Copilot plans page
• GitHub Copilot licenses (billing docs)
• Plans for GitHub Copilot (reference)
• Copilot usage-based billing announcement (April 2026)

Official References

• GitHub Copilot plans page (official)
• GitHub Copilot licenses — billing docs
• Usage-based billing announcement
• Plans for GitHub Copilot — docs

Related lessons: BE-02, BE-04, BE-06, BE-34