Who owns GitHub?

Microsoft owns GitHub. The acquisition was announced in June 2018 and closed that October, valuing GitHub at $7.5 billion in Microsoft stock. GitHub had spent its first decade as an independent company, founded in 2008 and venture-funded before the sale.

How much independence it kept, and for how long

For roughly seven years under Microsoft, GitHub ran as a distinct subsidiary with its own CEO and product direction. Nat Friedman ran the company from 2018 to 2021. Thomas Dohmke, previously GitHub’s chief product officer, took over next and led it through the launch and growth of Copilot.

That arrangement ended in August 2025. Dohmke stepped down, and Microsoft chose not to appoint another standalone GitHub CEO. GitHub’s leadership now reports into Microsoft’s CoreAI engineering organization, the group responsible for Microsoft’s AI platform and developer tools. GitHub still ships under its own brand and runs its own site, but organizationally it is no longer a semi-independent company inside Microsoft. It is part of Microsoft’s broader developer and AI operation in a much more direct way than it was for most of the first seven years.

What actually changed for developers

Two things worth knowing, one practical and one slower-moving.

The practical change came almost immediately: in January 2019, a few months after the deal closed, GitHub made private repositories free for every account, with no cap on how many you could create, and the remaining collaborator limits on free private repos went away within the following year. Before the acquisition, private repositories were the main thing individuals paid for. Removing that cost is a large part of why GitHub became the default place to keep even small personal projects, not just open-source work.

The slower change is integration. GitHub works closely with Visual Studio Code, which is also Microsoft’s, and Copilot, the AI coding assistant, launched on GitHub first and remains one of its flagship features. Neither required ownership to be possible, but ownership clearly accelerated both.

Whether any of this matters for your work there

The trust question behind most ownership searches is really: can I build years of work here, or could a corporate change put that at risk? The honest answer is that the platform’s core behavior, public repositories, issues, pull requests, the Git model underneath, has stayed stable through the founder era, the independent-subsidiary era, and two different Microsoft reporting structures.

There is also a structural reassurance that has nothing to do with corporate policy: every repository can be cloned in full, history included, at any time. Your commit history is exportable by design, so the platform does not hold anyone’s work hostage even in principle. Ownership changes affect product roadmaps; they have not affected whether the work stays yours.

Using what is already there

Regardless of who owns the platform, a GitHub account with real activity behind it, repositories, languages, a contribution history, is a genuinely useful record of your work. resumefromgit.com turns that record into a visual CV and a downloadable resume PDF, reading only from what GitHub already makes public, with no account or sign-up required on your end.