GitHub now gives users of its free plan access to unlimited private repositories, but those repos are limited to three collaborators apiece
Matthew Hughes / The Next Web :
Context & Ripple Effects
Private repositories were GitHub's core paywall: since unlimited private repos cost $7/month for personal accounts in 2016, solo developers paid simply to keep code out of public view. The pressure has been building on both sides — GitLab made its high-end tiers free for open source projects and schools last year, citing 100,000+ repos opened since Microsoft's acquisition news, while GitHub itself had already been widening the funnel through its developer program for non-paying users.
First-order effects
- Solo developers and tiny teams can now keep work private at $0, directly cannibalizing the personal-tier revenue GitHub established with its $7/month pricing.
Second-order effects
- The three-collaborator cap is the new upsell boundary: teams crossing it are pushed toward paid tiers like the $21/month Business plan with SAML and provisioning, while GitLab faces pressure to match free private repos or lose individual developers at the top of its funnel.
Third-order effects
- If the pattern holds, version-control hosting becomes a land-grab where the free tier defines the product and monetization migrates up-stack to team features, security tooling, and enterprise controls — making per-seat repo pricing structurally obsolete.
The trend: Code-hosting platforms are racing to the bottom on repository access, converting what was once the paid core into a free acquisition channel as GitLab and GitHub compete for developer mindshare.