Ghostty Is Leaving GitHub — And It's Not Just About Hosting

When most projects leave GitHub, it’s a footnote. When Mitchell Hashimoto’s project leaves GitHub, it’s a signal. The HashiCorp co-founder is pulling Ghostty — his GPU-accelerated terminal emulator — off the platform that hosts roughly every serious open-source project on Earth. This isn’t a hosting migration. It’s a vote of no confidence.

Why Ghostty Carries Weight

For the uninitiated: Ghostty is a native, GPU-accelerated terminal emulator that hit 1.0 in late 2024 and immediately became the talk of Hacker News and r/programming. Part of the buzz was technical — it’s genuinely fast and well-engineered. But the bigger reason was the author.

Hashimoto built Terraform, Vagrant, and Vault. He effectively defined the modern infrastructure-as-code playbook before stepping away from HashiCorp to write code on his own terms. Ghostty was that solo project, and within months it was being mentioned alongside Alacritty and WezTerm. So when this developer decides GitHub isn’t the right home anymore, it lands differently than yet another indie maintainer rage-quitting in a README.

The Microsoft Dependency Nobody Likes Talking About

GitHub became the de facto standard for open source after Microsoft acquired it in 2018. Code hosting, issue tracking, CI/CD via Actions, package registries, and now AI coding assistance through Copilot — the entire developer workflow now routes through one company in Redmond.

The contradiction is hard to miss. Open source was supposed to be decentralized. In practice, the global commons of free software runs on a single proprietary platform owned by one of the largest corporations on the planet. A policy change, a billing shift, or a suspended account is a single point of failure for projects that have spent a decade accumulating issues, PRs, and community history. Developers have been muttering about this for years. A few are now acting on it.

The Copilot Question Won’t Go Away

Then there’s Copilot. GitHub trained it on public repositories, and the licensing debate has never really cooled down. Code under GPL or MIT carries attribution requirements. A model that ingests that code and emits suggestions stripped of any license notice sits, at best, in a legal gray zone — one that GitHub and Microsoft have answered with corporate non-answers and a class-action lawsuit that’s still grinding through the courts.

The friction got sharper when Copilot went fully paid-tier and usage-based. The optics — “we trained on your free code, now we sell it back to you” — are difficult to defend in any developer Slack. For maintainers who care about the philosophical underpinnings of their work, that’s not a minor irritation. It’s the reason to leave.

The Alternatives Have Quietly Matured

Leaving GitHub used to mean stepping into the wilderness. That’s no longer true. Codeberg, run by a German non-profit on top of Forgejo, has become the de facto landing zone for projects exiting GitHub on principle. SourceHut offers a minimalist, email-driven workflow that purists love. Self-hosted Gitea and Forgejo instances are trivial to spin up.

The big institutional players already left, or never arrived. The Linux kernel runs its own git infrastructure. GNOME and KDE host on their own GitLab instances. The Free Software Foundation has Savannah. Codeberg’s pitch is structural: a non-profit cooperative can’t be acquired, can’t pivot to enterprise SaaS, and operates under EU data sovereignty rules. Where Ghostty actually lands isn’t confirmed yet, but the menu is real.

A Crack, or the Start of Something

One project leaving won’t dent GitHub. Hundreds of millions of repositories aren’t moving, and for most developers GitHub is the workflow — muscle memory, integrations, social graph, all of it. The friction of leaving is enormous, and most maintainers won’t pay it.

But influential developers tend to move first, and the rest of the ecosystem watches. Hashimoto already changed the shape of one industry. If the lesson of the last decade was that centralization is convenient, the lesson of the next one might be that convenience has a price tag — and it’s quietly going up. Where does your code live, and would it survive a change of ownership?