The Quiet Exodus: Why Developers Are Leaving GitHub

Developers are quietly packing their bags. For over a decade, GitHub has been where the world’s code lives. Now a growing slice of the open-source crowd is looking for the exit — toward names like Codeberg and toward hosting their own servers entirely. The interesting question isn’t just where they’re going. It’s why now.

Let me be straight with you: this isn’t a story that blew up on Hacker News last week. It’s a slow burn, one that’s been building for years. So instead of chasing a headline, let’s look at the structure underneath — the reasons this current keeps flowing.

Why GitHub, Why Now

For years, GitHub was simply the default. It’s where you pushed code, collaborated, and built a profile that doubled as a resume. Then Microsoft acquired it in 2018, and the mood shifted in subtle ways.

The heart of it is trust. Open-source developers tend to prize independence, and there’s something inherently uneasy about the world’s largest software company owning the world’s largest code repository. When everything lives in one place, that one place gets to change its mind — and everyone else lives with the consequences.

Two things poured fuel on the fire. One is the AI-training controversy that Copilot came to symbolize. The other is a much older anxiety: platform lock-in.

The Trigger: My Code Is Training Their AI

AI is the hottest flashpoint. GitHub Copilot autocompletes code by learning from publicly available code. The catch is that the “publicly available code” is, in large part, the open-source projects developers uploaded themselves.

For a lot of people, the math felt insulting: I gave this away for free, and a trillion-dollar company turned it into a paid product. There’s a licensing wrinkle too. Most open-source licenses ask for something in return — credit the source, or share derivatives under the same terms. But when an AI model absorbs your code and spits out a suggestion, the attribution evaporates. The chain of authorship simply disappears.

That’s where the sense of betrayal creeps in. Work contributed in a spirit of community became fuel for a commercial AI product, with nobody asked for permission. For many, that was the trigger — the moment “maybe I should move” turned into “I’m moving.”

Option One: Codeberg, a Code Commons Run by a Nonprofit

The first escape hatch is Codeberg, a code-hosting service run by a registered nonprofit association based in Germany. The whole pitch fits in one line: it is not a for-profit company.

Codeberg runs no ads. It doesn’t monetize your data. It won’t hand your code over for AI training. It survives on membership fees and donations instead. If GitHub is the classic “free, but you’re the product” model, Codeberg is closer to a library its members collectively own.

The limits are just as clear. It doesn’t have GitHub’s enormous user base, its sprawling CI/CD ecosystem, or its dense web of third-party integrations. The conveniences that come from sheer scale are hard to beat. So choosing Codeberg is less a bet on convenience and more a vote for a set of values.

Option Two: Forgejo, Your Own GitHub on Your Own Server

The second current skips hosted services altogether: self-hosting. Instead of renting space on someone else’s server, you stand up your own code repository on hardware you control. The star of this approach is Forgejo.

Forgejo is a fork of Gitea, an open-source project. When Gitea tilted toward commercialization, developers who wanted community-first governance split off and built Forgejo. And here’s the connective tissue: Codeberg itself runs on Forgejo. The two movements share a single root.

The appeal of self-hosting is total control. Where your code lives, who can touch it, what policies govern it — all of it is yours to decide. If a platform changes its pricing or kills a feature overnight, you don’t flinch. But there’s a bill to pay. Server maintenance, backups, security, updates — you own every bit of it. Freedom always comes with labor attached.

What’s Really Driving This: A Philosophy of Distribution

Step back and a bigger picture comes into focus. This isn’t really about swapping one service for another. It’s the revival of an idea: decentralization.

In the early internet, code was scattered across many servers. Git itself was built as a distributed system — the whole point was to collaborate without a central server. Then GitHub arrived and, paradoxically, pulled everything back into one place. The leave-GitHub movement is an attempt to scatter that concentration again.

A reality check, though. This is being driven by a minority — the values-forward wing of the open-source world, not the mainstream. For most companies and most developers, GitHub remains the overwhelming standard. Convenience and ecosystem are powerful weapons. So calling this a “mass exodus” overstates it. A quiet, steady drift is the more honest description.

The bottom line: developers aren’t leaving GitHub because it lacks features. They’re leaving over control, over trust, over the desire to hold their own code’s fate in their own hands. Whose server is your code sitting on right now? And have you ever really stopped to think about it? That question might just be where this whole movement begins.