GitHub Copilot costs $19 a month for an individual developer. That's the number everyone quotes, and it's accurate, but it's also the least useful part of the pricing story. The real cost depends on which GitHub plan you're already paying for, how many seats you're buying, and whether you're stacking it on top of Team or Enterprise licensing that has nothing to do with AI at all.
What $19/month actually buys
Copilot is never bundled into a GitHub plan. Free, Team at $4/user/month, and Enterprise at $21/user/month all handle repos, Actions minutes, and collaboration. Copilot is a separate line item on top of whichever of those an account already has. Pay the $4 for Team and then another $19/seat for Copilot, and the real per-seat cost for a Copilot-enabled developer is $23/month, not $19.
That $19 covers inline code completions in VS Code and JetBrains IDEs, a chat interface for asking questions about the current file or selection, and access to the underlying models GitHub has licensed for suggestions. It does not include GitHub's own core product. Buying Copilot without a GitHub account to attach it to isn't really an option since the extension authenticates against a GitHub identity either way.
Free accounts get a limited Copilot allocation now too: roughly 2,000 completions a month at no cost, enough to seriously test whether the suggestions are useful before paying anything. That's a meaningful change from Copilot's early years when there was no free tier at all, and it's the cheapest way to decide if the $19/month is worth it for a given workflow.
Business pricing works the same way
Copilot Business is priced at $19/user/month, the same rate as the individual plan. The difference isn't cost, it's administration: centralized billing, the ability to assign and revoke seats without touching individual GitHub accounts, and organization-wide policy controls like blocking suggestions that match public code verbatim. For a team of 10, that's $190/month for Copilot alone, again stacked on top of whatever GitHub Team or Enterprise licensing the org already carries.
There's no separately priced Enterprise tier for Copilot itself in GitHub's current structure. The distinction that matters is GitHub Enterprise ($21/user/month) versus GitHub Team ($4/user/month) as the base repo hosting plan, with Copilot added at the same flat $19/seat regardless of which one sits underneath it. Anyone budgeting for a large engineering org should plan around $19/seat for Copilot as a constant, then vary the base GitHub cost by which tier the org needs for security and compliance reasons unrelated to AI.
Real cost for different team sizes
A solo developer trying it out: the free tier's 2,000 completions a month is generous enough to run for a few weeks on a real side project before deciding whether $19/month is worth the recurring cost. Most developers know within a week whether the suggestions are saving real time.
A 10-person team already on GitHub Team ($4/user/month = $40/month base): adding Copilot Business for the whole team runs $190/month, bringing the combined GitHub bill to $230/month, or $2,760/year. That's the full cost of the tool, not just the AI feature by itself.
A 10-person team on GitHub Enterprise ($21/user/month = $210/month base): the same Copilot Business addition brings the total to $400/month, $4,800/year. The AI feature costs identically whether the base plan is Team or Enterprise, so the jump in total spend comes entirely from the underlying GitHub tier, not from Copilot.
A 50-person engineering org on Enterprise: base GitHub runs $1,050/month, Copilot Business adds $950/month, for a combined $2,000/month, $24,000/year. At that scale, the Copilot line item alone is a real budget conversation, not a rounding error.
What you're actually paying for versus what you're not
The $19/month buys inline completions and in-editor chat. It does not buy the kind of deep multi-file, whole-codebase editing that AI-native editors like Cursor or Windsurf are built around from the ground up. Copilot is fundamentally an extension layered onto an existing editor, and the pricing reflects a narrower feature set than a full AI-first IDE charging a similar or higher price. That's not necessarily a bad trade: a developer who doesn't want to switch editors gets AI assistance without disruption, and for routine autocomplete-style suggestions, Copilot's quality is genuinely competitive.
What the price doesn't include is any protection from GitHub's own account-level issues. Support response times for account problems have been a recurring complaint on r/github and Hacker News, sometimes stretching for weeks. Copilot access rides on the same GitHub account as everything else, so an account suspension takes Copilot down with it regardless of which pricing tier a team is paying for. That risk doesn't show up on the pricing page, but it's a real cost consideration for teams treating Copilot as essential daily tooling.
Where the free tier actually falls short
Free Copilot access at 2,000 completions a month sounds generous until a developer working on an active project burns through it in days rather than weeks. Heavy users doing significant daily coding will hit the ceiling fast and get bumped back to a degraded experience or blocked entirely until the next monthly reset. The free tier is genuinely useful for evaluation, not for treating as a permanent free alternative to the paid plan if the workflow involves real, sustained coding output.
There's also no partial-month proration path for teams growing mid-cycle: adding a new hire to Copilot Business typically starts billing at the next cycle boundary depending on how GitHub's billing system handles the specific org's plan, so teams onboarding several developers at once should check the exact proration behavior before assuming day-one costs.
What canceling actually looks like
Copilot is billed monthly with no long-term contract at the individual tier, so canceling stops the charge at the next billing cycle rather than mid-month. There's no confirmed annual-billing discount in GitHub's current pricing structure the way some competitors offer a yearly rate cut, so the $19/month figure is the number whether paying month to month or committing longer term. Business seats work the same way on the org side: removing a developer's Copilot access drops that seat from the next invoice, and GitHub's admin console handles the seat assignment without needing to contact support for routine additions or removals.
Downgrading from paid Copilot back to the free tier doesn't require canceling a GitHub account, since Copilot billing is entirely separate from repo hosting. A developer who decides $19/month isn't worth it keeps full access to their repos, Actions minutes, and everything else on whatever GitHub plan they're already paying for. That separation cuts both ways: it makes trying Copilot low-risk, but it also means the $19 never gets folded into a bigger platform discount the way some vendors bundle AI features into a higher-tier plan at a lower marginal cost.
Comparing the real number to alternatives
At $19/month, Copilot sits in the middle of the AI coding assistant market. Codeium's free tier matches Copilot's everyday completion quality for mainstream languages at zero cost, making it the obvious first stop for anyone Copilot-curious but price-sensitive. Cursor Pro costs $20/month, essentially the same price point as Copilot, but bundles a full AI-native editor with deeper multi-file context rather than an extension bolted onto VS Code. Windsurf undercuts both at $15/month for its Pro tier with comparable agentic editing capability.
The honest comparison isn't which tool is cheapest, since they're all within a few dollars of each other at the individual tier. It's what each price point actually buys: Copilot's $19 buys the lowest-friction path for teams that don't want to touch their existing editor setup, while the AI-native editors charge similar money for meaningfully deeper codebase understanding at the cost of switching tools entirely.
Is $19 a month worth it
For a team already standardized on VS Code or JetBrains and not looking to disrupt that setup, yes: $19/month per developer is a small fraction of a typical engineering salary, and even modest productivity gains on routine coding tasks justify the cost quickly. For teams open to switching editors entirely, it's worth testing Cursor or Windsurf's free tiers against Copilot's free allocation before committing, since the deeper multi-file editing in those tools can be worth the near-identical price for codebases where cross-file context actually matters.
The number to budget isn't $19. It's $19 plus whatever GitHub Team or Enterprise tier the org needs underneath it, multiplied by every seat that gets Copilot access. For a 10-person team on Enterprise, that's $4,800 a year for Copilot alone, a real number worth putting in front of finance rather than assuming it rounds to noise next to the rest of the engineering budget.