The Great GitHub Exodus: Why Developers Are Migrating to Codeberg and Beyond

GitHub has been the undisputed king of code hosting for over a decade. With 600 million repositories, a billion commits in 2025 alone, and a new user joining every second, its dominance seems unshakeable. But something quieter has been happening beneath the surface — a growing trickle of high-profile projects packing up and leaving.

The question isn't just about where code lives. It's about who controls the infrastructure that the entire open-source world depends on, and what happens when that trust starts to erode.

The Departures So Far

The most notable exit came from Ghostty, a cross-platform terminal emulator created by Mitchell Hashimoto, co-founder of HashiCorp. In April 2026, Hashimoto announced that Ghostty would be leaving GitHub entirely, though gradually. "It's not a fun place for me to be anymore," he wrote. "I want to be there but it doesn't want me to be there. I want to get work done and it doesn't want me to get work done."

Ghostty wasn't alone. Zig, a systems programming language positioned as a spiritual successor to C, announced its departure back in November 2025. Tenacity, a cross-platform audio editor, made the switch even earlier. The Dillo web browser and the Hare programming language have also migrated. Even projects that were never on GitHub — like GNOME and Apache's vast software portfolio — have been self-hosting for years, and their stance is looking increasingly prescient.

Why Developers Are Walking Away

The reasons for these migrations aren't abstract ideological posturing. They fall into three concrete categories:

• Reliability: GitHub suffered 112 hours of downtime across 48 major outages between May 2025 and May 2026, according to IncidentHub tracking. For maintainers who rely on the platform for their daily workflow, each outage is a productivity killer. Both Ghostty and Zig explicitly cited reliability as a driving factor.
• AI encroachment: GitHub has leaned hard into AI integration with Copilot, and the rhetoric has gotten increasingly aggressive. CEO Thomas Dohmke's 2025 comment — "Either you embrace AI, or get out of this career" — alienated a significant portion of the developer community. For projects that view AI-generated code as a quality and licensing risk, GitHub's direction feels hostile.
• Politics and ownership: Since Microsoft's acquisition, concerns have simmered about GitHub's corporate relationships, including a controversial deal with ICE that drew internal protests in 2019. The Zig project's departure statement referenced GitHub's relationship with ICE. More broadly, developers worry about a single corporation controlling the infrastructure of open source.

Where Are They Going?

The alternatives fall into a few buckets:

• Codeberg: A non-profit, community-run platform built on Gitea. It's become the most popular landing spot for migrating projects because it offers a familiar Git-based workflow without corporate ownership. Codeberg is funded by donations and run by a German non-profit, meaning its incentives align with users rather than shareholders.
• Self-hosting: Projects like GNOME use GitLab's community edition on their own servers. This gives maximum control but requires infrastructure investment and ongoing maintenance.
• SourceHut: A minimalist, email-driven development platform that rejects JavaScript and modern web bloat entirely. It's not for everyone, but it represents a philosophical counterpoint to GitHub's everything-in-one-platform approach.
• Read-only GitHub mirrors: Many departing projects keep a mirror on GitHub for discoverability while moving active development elsewhere. This is a pragmatic compromise — you get the network effect without the dependency.

The Network Effect Problem

Here's the uncomfortable truth: GitHub's biggest moat isn't its features. It's the network effect. Open source works through discoverability, collaboration, and contribution. When every project is on GitHub, finding code, submitting patches, and building on others' work all happen in one place. Leaving means giving up that ecosystem.

This is why most departing projects maintain read-only mirrors. Ghostty's migration plan explicitly acknowledges this — they're keeping a GitHub presence for visibility while moving the actual work elsewhere. It's a hedge that reflects the reality: you can leave GitHub, but you can't fully escape its gravity.

What This Means for the Broader Ecosystem

The exodus is still a trickle, not a flood. The vast majority of open-source projects — including some of the most important ones — remain on GitHub. But trends start with trickles. The Linux kernel never fully embraced GitHub, maintaining its own infrastructure at kernel.org. Major projects are now demonstrating that life after GitHub is possible, and the alternatives are mature enough to support real development workflows.

The deeper lesson is about platform risk. When a single platform becomes essential infrastructure, the entity controlling it has enormous leverage. Microsoft's choices around AI, monetization, and corporate partnerships don't align with every developer's values — and for those developers, the cost of staying is starting to outweigh the cost of leaving.

For individual developers and small projects, this is mostly an observer story. For maintainers of significant open-source projects, it's worth thinking about your platform dependencies. Even if you stay on GitHub, having a migration plan — or at least maintaining your own backups and mirrors — is just good infrastructure hygiene.

The Bottom Line

GitHub isn't dying. But the assumption that it's the only viable home for open source is finally being tested. Projects like Ghostty and Zig are proving that alternatives like Codeberg and self-hosted GitLab can support real development at scale. Whether that trickle becomes a flood depends on what GitHub does next — and whether the open-source community decides that owning its infrastructure is worth the extra effort.

The most interesting outcome wouldn't be a mass exodus. It would be a healthy ecosystem where GitHub is one option among many, and where the most important code isn't hostage to any single corporation's priorities. That's an outcome worth working toward — whether you're a project maintainer weighing a move or a developer choosing where to contribute.