Originally reported by The Register. Original article published April 2020.
What GitHub Changed
In April 2020, GitHub announced a significant restructuring of its pricing and free tier. The headline changes were:
- Private repositories with unlimited collaborators became free — previously this required a paid Team plan.
- Free tier includes 500 MB of GitHub Packages storage.
- Free tier includes 2,000 minutes of GitHub Actions per month for automated CI/CD workflows.
- The paid Team plan dropped from $9 to $4 per user per month, adding 2 GB package storage, 3,000 Actions minutes, and GitHub support.
- The Enterprise plan remained unchanged at $21 per user per month, covering security, compliance, and higher usage quotas.
A Brief History of GitHub’s Pricing Evolution
Before Microsoft acquired GitHub, the model was straightforward: public (open-source) repositories were free, private repositories were paid. After the acquisition closed, GitHub CEO Nat Friedman announced in January 2019 that private repositories with up to three collaborators would become free. The April 2020 announcement removed the collaborator limit entirely, extending the free tier to teams of any size.
The GitLab Factor: Why the Timing Matters
The pricing changes did not happen in a vacuum. GitLab — GitHub’s most direct competitor and a platform that markets itself as providing “the entire DevOps lifecycle in a single application” — had already been offering a comparable free tier. GitLab’s free plan included:
- Unlimited private and public repositories
- Unlimited collaborators
- 2,000 CI pipeline minutes per group per month on shared runners
Notably, GitLab’s paid Bronze plan — aimed at small teams — was already priced at $4.00 per user per month, exactly matching GitHub’s newly reduced Team plan. Whether or not GitHub’s pricing team looked directly at GitLab’s rate card, the alignment is difficult to dismiss as coincidence.
Microsoft’s Strategic Rationale
Friedman framed the announcement around access: “every developer on Earth should have access to GitHub. Price shouldn’t be a barrier.” That is a genuine philosophical position, but it also serves a clear commercial purpose.
Microsoft has described GitHub as a strategic asset that supports its broader developer ecosystem — including Azure cloud services and the Visual Studio / Azure DevOps toolchain. CEO Satya Nadella characterised the combined offering as “a compelling developer SaaS solution,” while simultaneously emphasising that developers using Microsoft tools can “target any cloud, any edge device.” The dual message — openness for developers, ecosystem stickiness for investors — reflects the tension at the heart of Microsoft’s GitHub ownership.
Keeping developers on GitHub, especially early-career and open-source developers who may later influence enterprise purchasing decisions, has long-term value even when those users pay nothing today.
GitHub Actions and the CI/CD Race
GitHub introduced Actions in August 2019, bringing native CI/CD workflows directly into the platform. Before Actions, teams typically had to integrate third-party tools (Travis CI, CircleCI, Jenkins, and others) or move to a platform like GitLab that had built-in pipelines from the start. Including 2,000 free Actions minutes in the new free tier was a direct move to close that competitive gap and reduce a key reason teams might choose GitLab over GitHub.
The npm Acquisition: Expanding the Ecosystem
The pricing changes came shortly after GitHub announced an agreement to acquire npm, the dominant package registry for the JavaScript ecosystem. Together, free private repositories, built-in CI/CD, integrated package management, and a large existing developer community reinforce GitHub’s position as the default home for code — making it harder for any single competitor to displace it.
What This Means in Practice for DevOps Teams
For individual developers and small teams, the free tier changes are genuinely useful. Unlimited private collaborators and 2,000 CI minutes per month cover a significant portion of real project needs without cost.
For professional and enterprise DevOps teams, pricing is rarely the deciding factor. Reliability, security controls, compliance features, integration depth, and support SLAs matter more. GitHub’s history of platform incidents (outages, degraded performance) remained a legitimate concern for teams evaluating it as a mission-critical platform, regardless of how attractive the free tier became.
The competitive picture in 2020 was essentially this:
- GitHub: largest developer community, strong ecosystem, improving CI/CD, free tier now matches GitLab’s.
- GitLab: more mature built-in DevOps tooling, self-hosted option, strong in enterprises that want a single integrated platform.
- Both: competing hard at the free tier to attract developers early, with the expectation that team and enterprise upgrades follow.
Summary
GitHub’s April 2020 pricing overhaul — free unlimited private repositories, 2,000 Actions minutes, and a $4 Team plan — brought it into direct parity with GitLab’s free and entry-level paid tiers. The move reflects both genuine democratisation of developer tooling and a calculated competitive response to GitLab’s longstanding advantages in CI/CD and all-in-one DevOps workflows. For DevOps practitioners, the practical takeaway is that the cost barrier to using either platform for private team projects effectively dropped to zero, shifting the evaluation criteria squarely onto features, reliability, and integration fit.