Microsoft Now Owns GitHub AND GitLab. Should Developers Be Worried?

The FTC reviewed the deal under its standard merger guidelines and cleared it without conditions. The European Commission was more cautious, approving the acquisition but attaching 5-year interoperability requirements: Microsoft must maintain open APIs that allow third-party CI/CD tools, security scanners, and IDE integrations to work with GitLab on the same terms as Microsoft's own products. [1] That's a meaningful safeguard — for five years. What happens in year six is anyone's guess.

The sentiment gap

Here's the part of this story that doesn't fit neatly into either the "Microsoft is evil" or "Microsoft has changed" narrative: developers are saying one thing and doing another. [3] Stack Overflow's February 2026 developer survey found that 42% of respondents were "concerned" or "very concerned" about data privacy implications of the acquisition. On Hacker News, the deal announcement generated over 5,000 comments, with the dominant themes being "GitLab sold out," "Microsoft will enshittify it," and calls to migrate to self-hosted alternatives like Gitea, Forgejo, or Codeberg. But here's what actually happened to GitLab's numbers: adoption rose 12% in Q1 2026. New team signups accelerated. Enterprise contract renewals held steady. This isn't hypocrisy. It's the difference between principles and switching costs. Moving a development team's entire workflow — repositories, CI/CD pipelines, issue tracking, code review processes, security scanning configurations — from one platform to another is a multi-week project for a small team and a multi-month project for a large one. The inconvenience of staying is almost always less than the inconvenience of leaving, especially when the platform still works fine. That calculation might change if Microsoft starts degrading the product. But in the near term, the loudest critics and the actual users are mostly different populations.

What Microsoft actually controls now

Let's lay out the full picture, because individual acquisitions often look reasonable while the aggregate looks different. Microsoft now owns or controls: • GitHub — The dominant source code hosting platform (100M+ developers, 400M+ repositories) • GitLab — The second-largest code hosting and DevOps platform (30M+ users) • VS Code — The most popular code editor in the world (used by ~73% of developers per Stack Overflow) • npm — The package registry for JavaScript and TypeScript, the world's most-used programming languages • TypeScript — The language itself, which has become the default for new web projects • GitHub Copilot — The leading AI code assistant • LinkedIn — Where developers find jobs and recruiters find developers • Azure — The second-largest cloud platform, where code gets deployed • Azure DevOps — Enterprise CI/CD and project management [2] Each of these was acquired or developed independently, and each serves a legitimate business purpose. Microsoft hasn't done anything overtly anticompetitive with any of them — GitHub is arguably better under Microsoft ownership than it was before, and VS Code is genuinely open-source. But infrastructure is about trust, and trust is about alternatives. When one company owns both the road and the only two gas stations, the fact that gas is currently cheap doesn't mean you shouldn't be paying attention.

The open-source question

GitLab's core value proposition has always been its open-core model. GitLab Community Edition (CE) is open-source under an MIT license — anyone can download it, modify it, and run it on their own servers. GitLab's paid tiers (Premium and Ultimate) add proprietary features on top of that open-source foundation. [1][2] Microsoft has pledged to maintain this structure. GitLab CE will remain open-source. Self-hosted deployments will continue to be supported. The company will operate as a "semi-independent subsidiary" under Azure DevOps, with its own brand, pricing, and product roadmap. These are the right commitments. The question is whether they'll hold. Microsoft's track record here is genuinely mixed. On one hand, the company has become one of the largest contributors to open-source software in the world. GitHub under Microsoft launched Copilot, improved GitHub Actions, and invested heavily in security features. VS Code remains MIT-licensed and community-driven. On the other hand, Microsoft has a decades-long history of embrace-extend-extinguish strategies with competing platforms, and the company's incentives don't always align with keeping alternatives viable. The EU's 5-year interoperability mandate provides a hard floor. But five years in tech is both a long time and no time at all. The developers who are worried aren't worried about tomorrow — they're worried about 2031.

Who benefits, who loses

Enterprise customers probably benefit in the short term. Microsoft has the resources to accelerate GitLab's AI features, improve its cloud infrastructure, and offer deeper integrations with Azure. If you're a Fortune 500 company already running on Microsoft's stack, having GitHub and GitLab under one roof simplifies vendor management and potentially reduces costs. [2] Self-hosted users are the group to watch. GitLab's self-hosted deployment option is critical for government agencies, defense contractors, financial institutions, and any organization with strict data sovereignty requirements. Microsoft has committed to maintaining it, but self-hosted support is expensive and generates less recurring revenue than cloud subscriptions. The economic incentives to gradually degrade self-hosted in favor of cloud are real, even if the stated commitment is genuine. Open-source alternatives are the surprise beneficiaries. Gitea, Forgejo, and Codeberg have all reported significant increases in signups since the acquisition was announced. Forgejo in particular — a community fork of Gitea that emphasizes governance independence — saw a 300% increase in new installations in the week following the deal's close. [3] These are still tiny compared to GitHub and GitLab. But they represent exactly the kind of ecosystem diversity that keeps dominant platforms honest. If Microsoft missteps, the alternatives exist. They just need to be good enough that migrating to them isn't a heroic act. Individual developers lose optionality. Not immediately, and not dramatically — but the comfort of knowing that two competing platforms keep each other honest is gone. Competition was the mechanism that ensured features got built, prices stayed reasonable, and open-source commitments were maintained. That mechanism is now weaker.

The real test isn't technical

Microsoft will almost certainly make GitLab a better product in the near term. More AI features. Faster CI/CD runners. Better Azure integration. Improved security tooling. The company has the engineering talent and the financial resources to do all of this, and it has every incentive to justify a $45 billion price tag with visible improvements. The real test is structural. Will Microsoft maintain GitLab's independence when the two platforms' roadmaps conflict? Will self-hosted remain a first-class option when cloud generates more revenue? Will the open APIs stay open when proprietary integrations could drive Azure adoption? Will GitLab CE continue to receive meaningful updates when the commercial incentive is to push users toward paid tiers? None of these questions have answers today. They'll be answered over the next three to five years, one product decision at a time, mostly in ways that won't make headlines.

What developers should actually do

If you're running production workloads on GitLab, don't panic-migrate. The platform works. It's going to continue working. The EU interoperability requirements provide real (if time-limited) protection. But this is a good time to audit your dependencies. How much of your development stack runs through Microsoft? If the answer is "most of it" — VS Code, GitHub or GitLab, npm, Azure, Copilot — that's not necessarily a problem today, but it's a concentration risk worth understanding. Keep an eye on the self-hosted options. Know what Forgejo and Gitea look like. Understand what a migration would involve. You probably won't need to do it. But the developers who have a plan are the ones who have leverage — and leverage is what keeps platforms accountable, even friendly ones. The $45 billion question isn't whether Microsoft will ruin GitLab. It's whether the developer ecosystem can stay healthy when one company owns this much of the foundation. History suggests caution. Microsoft's recent track record suggests optimism. The truth is probably somewhere in between — and it'll take years to know which.