Developers Are Done Trusting GitHub (And They’re Leaving)
Not a mass exodus, but a quiet rebellion against corporate control over open source.
For over a decade, GitHub has been the default home for software. Need to collaborate? Ask GitHub. Want contributors? Use GitHub. Build a portfolio? Use GitHub.
It became less a tool and more a gatekeeper.
But here is the uncomfortable truth: a growing number of developers do not trust it anymore, and they are quietly moving their projects elsewhere, to places like Codeberg, Forgejo, and GitLab.
Not because those platforms are flashy.
Because they feel safer there.
Open source built the house, a corporation owns it
When Microsoft bought GitHub, the message to many developers was clear: the world’s largest open-source hub now answers to a trillion-dollar company.
Yes, Microsoft has mostly kept GitHub running smoothly. The sky did not fall.
But open source has always been about independence. The idea that the central meeting place for developers is controlled by one corporation makes some people deeply uncomfortable, especially when their projects, communities, and histories tie to that platform.
You do not have to hate Microsoft to feel uneasy about that level of power.
GitHub is turning into a product, not a community
GitHub used to feel simple: repositories, issues, pull requests. Done.
Now it feels like a full-blown enterprise platform stuffed with dashboards, AI assistants, security alerts, project boards, and monetization hooks. For big companies, that’s great. For individual developers, it can feel like using a spaceship to go to the grocery store.
Some people just want a clean place to host code, not a constantly evolving productivity ecosystem.
Alternatives often win simply by being boring.
The AI push crossed a line for some people
AI coding tools are powerful, but they are also controversial. Many developers worry about models trained on public repositories without explicit consent. Others dislike having embedded AI features in their workflow whether they want them or not.
For programmers who believe strongly in licensing, attribution, or the human side of coding, this feels less like innovation and more like appropriation.
So they leave, not loudly, not dramatically, just quietly moving their projects somewhere AI is not baked into every corner.
Vendor lock-in is real and people are waking up
Git itself is decentralized. GitHub is not.
When your issues, pull requests, discussions, CI pipelines, and community all live on one platform, moving becomes painful. That is vendor lock-in.
Platforms like Forgejo and Codeberg lean into portability and self-hosting. If something goes wrong, you can move or run your own instance.
It is the difference between owning your tools and renting them.
Smaller platforms feel like communities again
On big platforms, your project competes with millions of others. Visibility becomes a numbers game. Everything feels optimized for scale.
On nonprofit or self-hosted forges, interactions often feel more human. Maintainers are not just usernames lost in a sea of activity. Discussions are calmer. Expectations differ.
It feels less like posting on a corporate network and more like working in a shared workshop.
But let’s be honest: GitHub still has gravity
Most developers are not deleting their accounts; GitHub’s network effect is massive.
Recruiters check GitHub profiles.
Tutorials assume GitHub links.
Recruiters check GitHub profiles.
Tutorials assume GitHub links.
Tools integrate with GitHub first.
Contributors already have accounts there.
Leaving completely can make a project harder to find and contribute to.
So many teams hedge their bets: they mirror repositories, keep GitHub as a public face, or move gradually.
This isn’t a boycott, it’s a loss of faith
Nobody is organizing a grand anti-GitHub movement. There is no single breaking point.
Instead, it is thousands of individual decisions:
“I’d rather host this somewhere else.”
“I want control over my infrastructure.”
“I dislike the platform's direction.”
Each move is small. Together, they form a pattern.
The real issue isn’t features, it’s power
At the heart of this shift is a simple question:
Should open source infrastructure be owned by one company?
Some developers are answering “no" not with speeches, but with migrations.
GitHub isn’t collapsing. It will likely remain dominant for years, but the idea that it is the only serious home for code is fading.
Open source was never meant to live in a single location.
And now, slowly, it is not.
Summary: Developers aren’t fleeing GitHub overnight, but many are diversifying where their code lives due to concerns about corporate control, AI direction, lock-in, and platform complexity. The result is a quieter, more decentralized ecosystem where no single forge fully dominates.
