GitHub Enterprise pricing starts at $21 per user a month for the first 12 months, against $4 per user a month for GitHub Team on the same terms. SAML single sign-on is only on Enterprise (GitHub Enterprise Cloud), so for a team that wants SSO, the upgrade costs $17 more per developer a month: $4,080 a year for 20 developers, $2,040 for 10.
Those are the prices on GitHub's pricing page as we read it on 27 October 2026. Below: what Team already includes, what Enterprise adds besides SSO, how SAML and SCIM work on GitHub, how to remove people without them, and when Team is enough.
GitHub's plans and prices
| Plan | Price | SSO |
|---|---|---|
| Free | $0 | No |
| Team | $4 per user a month, for the first 12 months | No |
| Enterprise | From $21 per user a month, for the first 12 months | SAML SSO, SCIM |
GitHub shows both paid prices with a "for the first 12 months" note and an asterisk, and the page we read doesn't say what they become after that. Treat the figures below as year-one prices and check the current terms with GitHub before you budget beyond a year. Enterprise is per user, like Team, so the difference grows with every engineer you hire.
For a growing team, the first-year cost of moving from Team to Enterprise:
| Developers | Team | Enterprise | Difference |
|---|---|---|---|
| 5 | $240 | $1,260 | $1,020 |
| 10 | $480 | $2,520 | $2,040 |
| 20 | $960 | $5,040 | $4,080 |
| 40 | $1,920 | $10,080 | $8,160 |
| 50 | $2,400 | $12,600 | $10,200 |
The sums: $21 minus $4 is $17 per developer a month, or $204 a year. Twenty developers: 20 × $204 = $4,080. Fifty: 50 × $204 = $10,200.
What Team already includes
Before you price the upgrade, look at what $4 a seat buys. On the pricing page as we read it on 27 October 2026, Team includes repository rules, required reviewers (a set number of approvals before changes reach a protected branch), code owners, multiple reviewers and draft pull requests, Pages and wikis, environment deployment branches and secrets, 3,000 CI/CD minutes a month and 2 GB of Packages storage. GitHub Secret Protection and GitHub Code Security are sold as add-ons on Team.
That is most of what a small engineering team needs to keep its code safe from its own mistakes. What Team does not have is anything that ties GitHub accounts to your company's identity provider.
What Enterprise adds
SAML SSO is the headline, but it is not the only thing on the Enterprise card. Identity comes first: SAML single sign-on, user provisioning through SCIM, and Enterprise Managed Users, where your identity provider creates and owns the GitHub accounts. For running several teams there is an enterprise account to manage multiple organizations together, plus GitHub Connect. On governance, Enterprise adds environment protection rules, repository rule insights, the Audit Log API and advanced auditing. For compliance, it lists data residency on Microsoft Azure regions, SOC 1 and SOC 2 Type 2 reports every year, and FedRAMP Tailored authorization. And for scale, it raises the allowances to 50,000 CI/CD minutes a month and 50 GB of Packages storage, with premium support as an add-on only Enterprise can buy.
If several of these matter to you, Enterprise may be worth it regardless of SSO. A team whose CI regularly burns through Team's 3,000 minutes, or whose customers keep asking for GitHub's own SOC 2 report, has real reasons to move. If SSO is the only reason, you are paying the SSO tax: $17 a developer a month for a login feature.
SAML SSO on GitHub
With SAML SSO on an Enterprise Cloud organization, members keep their own personal GitHub accounts, but to see the organization's private repositories they must also authenticate through your identity provider. Each person links their GitHub account to their company identity once; after that, GitHub checks the company session periodically.
Two things catch people out. First, it does not create GitHub accounts. People still sign up for GitHub themselves and are invited into the organization; SAML only controls whether their existing account can reach your organization's resources. Second, it does not remove members on its own. If someone leaves and you disable them in the identity provider, they lose access to your organization's resources the next time GitHub checks their SSO session, but they remain a member, holding a seat, until they are removed.
GitHub also offers Enterprise Managed Users, where the identity provider owns the GitHub accounts themselves. That gives the most control and is the heaviest to set up. For a small team it is rarely the right starting point.
SCIM on GitHub
Removing members automatically needs SCIM on top of SAML. GitHub's article about SCIM for organizations, as we read it on 27 October 2026, says SCIM lets administrators "add, manage, and remove organization members' access to GitHub" from the identity provider. It lists three supported providers for organizations that use personal accounts: Microsoft Entra ID, Okta and OneLogin. Without SCIM, the article says, members whose identity provider access is removed "aren't automatically removed from the organization" when their sessions expire; an owner has to remove them on GitHub.
That is the same split you see everywhere: SAML is the door, SCIM is the guest list. Our post on SCIM vs SAML explains why you usually need both to get the outcome people buy SSO for.
Removing people from a GitHub organization
On any plan, including Free and Team, an organization owner can remove a member by hand. GitHub's removal guide gives the path. Click your profile picture, choose Organizations, and open your organization. Under its name, click People. Tick the box next to each person you want to remove, open the members selected dropdown above the list, choose Remove from organization, review the list and confirm with Remove members.
They lose access to the organization's repositories, including their forks of its private repositories; they may keep local copies but can't sync them, and GitHub notes that making sure they delete confidential material is your job. Invitations they sent that nobody accepted are canceled. GitHub keeps their membership details for three months, so if they come back in that time their previous access can be restored. If you pay for a fixed number of licenses, removing a member does not reduce the count on its own; lower it in billing.
A few things deserve a look when someone leaves, whatever your plan. Outside collaborators are people added to individual repositories without being organization members; they are listed separately and are easy to miss. Tokens and keys need checking too: removing the member cuts off their personal access tokens' and SSH keys' access to your organization's repositories, but deploy keys and machine users they set up keep working. Apps they authorized for the organization, GitHub Apps and OAuth apps alike, may still be acting on your code. And repository ownership matters: if they own repositories under their personal account that your team depends on, transfer them before they go.
Contractors deserve their own habit. An agency developer added as an outside collaborator to one repository for a project never appears in the member list, so a removal routine that only looks at members misses them. Our guide to contractor access management covers how to keep that list short, and our employee offboarding checklist covers the rest of the leaver steps across your tools.
The login control Team already has
Team can't force SAML, but it can force two-factor authentication. GitHub's guide to requiring 2FA in your organization puts it in the organization's Settings, under Authentication security: tick "Require two-factor authentication for everyone in your organization" and save. As we read it on 27 October 2026, members and billing managers without 2FA keep their membership and their seat but can't reach the organization's resources until they turn it on. Outside collaborators without 2FA are removed from the organization, and can be reinstated within three months once they enable it.
Turn that on before anything else. Our post on SSO vs MFA explains how much of the login risk it covers on its own.
When Team is enough
GitHub Team is enough for most small engineering teams when four things are true. The first is that no customer contract or auditor requires SAML for access to your code. SOC 2 asks that you control and review access and remove it promptly; it does not name SSO, and a logged removal process can show that (our post on SSO for SOC 2 has the detail). The second is that everyone uses 2FA, enforced at the organization as above. The third is that you remove leavers the same day, by hand from the People page or with tooling that does it for you. The fourth is that you review members regularly: a quarterly user access review catches outside collaborators and forgotten accounts.
Enterprise starts to pay for itself when you need several of its features at once, when you run multiple organizations, or when you are large enough that SCIM-driven provisioning saves real hours every month. A 5-person startup with one organization and no enterprise customers is almost always fine on Team; a 50-person company selling to banks may not be. Run your whole stack through the SSO tax calculator before deciding: GitHub is usually one of several tools asking for the same upgrade.
Where SmashSSO fits
SmashSSO adds and removes people in your GitHub organization from the same place as every other tool, on the plan you already have. It reads your people from Google Workspace, reads your organization's members and roles, and matches them to your people (GitHub accounts are often personal, so any that match nobody are flagged for you to check); a departed engineer still in the organization shows up next to everyone else they still have access to. Inviting, changing roles and removing run through GitHub's API when you add a token, or through an agent in your own Chrome where you are already signed in as an owner. Inviting someone into a paid seat waits for your approval, and every change goes into an audit log.
It does not give you SAML. If you need enforced SSO for GitHub, you need Enterprise. If what you need is that nobody who left is still in the organization, SmashSSO does that for a flat fee from $199 a month billed annually, for the whole company (pricing).