GitLab's high-end plans are now free for open source projects and schools, and the company says 100,000+ repos have been opened since GitHub acquisition news
Frederic Lardinois / TechCrunch :
Context & Ripple Effects
GitLab has spent three years positioning itself as the open-source counterweight to GitHub, raising a $20M Series B led by August Capital and then a Series C led by GV with Matt Mullenweg joining the board. Along the way it built bridges rather than walls — including a move to run its continuous integration and delivery features against code hosted on GitHub.
With Microsoft's acquisition of GitHub rippling through the developer community, GitLab is now converting that anxiety into migrations: it reports 100,000+ new repositories opened since the deal news, and is removing the price barrier by making its high-end plans free for open source projects and schools.
First-order effects
- Open source maintainers and educational institutions get GitLab's paid-tier features at no cost immediately, lowering the switching cost for the 100,000+ repos already opened since the acquisition announcement.
- GitHub faces direct churn pressure at the exact moment its user base is reassessing ownership, with GitLab's existing CI/CD integration serving as a ready-made landing path.
Second-order effects
- GitHub is pushed to compete on trust and roadmap independence rather than features alone, since GitLab can now match premium tiers for the segments most sensitive to acquisition risk.
- GitLab's free-for-open-source tier turns its paid plans into an enterprise upsell funnel, pressuring pricing across the code-hosting market for commercial customers too.
Third-order effects
- If the migration pattern holds, code hosting commoditizes further and differentiation shifts to the surrounding DevOps toolchain — CI/CD, chat (as in GitLab's earlier Gitter acquisition), and deployment — rather than repository storage itself.
- Developer-platform consolidation under large acquirers may structurally strengthen independent, open-core alternatives, making 'who owns your forge' a recurring procurement question for projects and schools.
The trend: Code hosting is shifting from a repository-storage business to a DevOps-platform contest, where acquisition events trigger waves of migration that open-source challengers convert into share.