Two days ago, GitHub made an announcement that would have been unthinkable just a few years back: all of GitHub’s core features are now free for everyone, including teams. Unlimited private repositories with unlimited collaborators. No paywall. Let that sink in for a moment.
If you’d told me in 2015 that Microsoft would buy GitHub and then proceed to make it more open and accessible, I’d have questioned your judgement. Yet here we are, and this move feels like a genuine inflection point for how we think about developer tooling and collaboration.
What Actually Changed#
The details matter here. GitHub Free now includes unlimited private repositories with unlimited collaborators — something that previously required a paid Team plan. The new GitHub Free for organizations also bundles in 2,000 Actions minutes per month and 500MB of GitHub Packages storage. For many small teams and startups, this eliminates the single biggest reason to look elsewhere.
The paid Team plan itself dropped from $9/user/month to $4/user/month, adding features like code owners, required reviewers, and draft pull requests. Enterprise features remain separate, naturally — GitHub still needs revenue. But the core collaboration workflow? That’s now free.
This is significant because it removes friction at exactly the point where developers make tooling decisions. When you’re starting a side project with a few friends, or bootstrapping a startup, or running an open source project that needs some private CI infrastructure — you no longer hit that awkward moment where someone has to pull out a credit card.
The Strategic Play#
Let’s be honest about what’s happening here. GitHub has 56 million developers on the platform. Microsoft’s play isn’t about charging $4/user/month for private repos — it’s about making GitHub the default collaboration layer for every developer on the planet, then building enterprise services on top of that foundation.
Actions, Packages, Codespaces (still in beta), the security advisory database, the dependency graph — these are the revenue drivers. The basic Git hosting and collaboration? That’s the moat. By removing the last friction point for teams, GitHub is effectively saying: “We don’t want anyone to have a reason not to be here.”
From a competitive standpoint, this puts serious pressure on GitLab and Bitbucket. GitLab has been winning deals with teams who couldn’t justify GitHub’s per-seat pricing, especially in the CI/CD space where GitLab’s integrated pipelines were compelling enough to offset the less polished UI. Now that calculus changes. GitHub Actions is maturing rapidly, and with free private repos, the “GitLab is cheaper” argument largely evaporates.
What This Means for the Ecosystem#
I’ve been running a mix of GitHub and self-hosted Gitea instances for various projects. The self-hosted approach made sense when private repos on GitHub meant paying per seat — especially for IoT projects where I wanted to keep firmware code private but didn’t want to justify the cost for a two-person side project.
With this change, I’m genuinely reconsidering that setup. Self-hosting a Git server isn’t hard, but it’s one more thing to maintain, one more thing to back up, one more thing to keep patched. If GitHub offers equivalent functionality for free, the operational overhead of self-hosting becomes harder to justify unless you have specific compliance or data sovereignty requirements.
For the broader open source community, this is almost entirely positive. Projects that maintained awkward split workflows — public repos for code, private repos elsewhere for CI configs or deployment scripts — can consolidate. Teams that were using GitHub for open source but Bitbucket for private work can simplify their toolchain.
The 2,000 Actions minutes per month is particularly interesting. That’s enough for a reasonable CI/CD pipeline for a small project. Not enough for heavy integration testing or nightly builds across multiple platforms, but enough to get started without any cost. Combined with the existing free tier for public repos (which already had unlimited Actions minutes), this makes GitHub a genuinely complete platform for small-to-medium projects.
My Take#
I’ve been in this industry long enough to remember when free services from large companies felt like traps. And maybe there’s an element of that here — once your entire workflow is on GitHub, the switching costs are enormous, and Microsoft knows it. But I also think there’s a more pragmatic reading: developer tools are becoming infrastructure, and the economics of infrastructure favor scale and low margins on the base layer.
GitHub making core features free is good for developers. Full stop. The question isn’t whether to be grateful — it’s whether to be cautious. I’d still recommend that teams maintain the ability to export their repos and CI configurations. Don’t build workflows that are impossible to migrate. Use standard tooling where you can.
But for right now? If you’re a small team weighing GitHub against alternatives, the math just got a lot simpler. The platform is strong, the ecosystem is deep, and the price is right. Sometimes the boring, obvious choice is also the correct one.
The timing during a global pandemic — when countless developers are working from home and collaboration tooling matters more than ever — feels deliberate. Smart move, GitHub.