The Linux Distro Graveyard — The Numbers Are More Telling Than You Think
I've been using Linux since the Yggdrasil and early Slackware days, so I've watched a lot of distros come and go over the decades. I always suspected the attrition rate was bad, but I decided to actually dig into the numbers recently — and they're more sobering than I expected.
According to DistroWatch data analyzed in early 2024, of 958 total distributions ever tracked, only 274 are still active. 637 are officially discontinued, and another 47 are listed as "dormant" — meaning they might come back someday, but don't hold your breath. That's a survival rate of under 30%. Nearly 70% of every Linux distro ever created is dead.
The peak was actually back in 2011, when 323 distros were active simultaneously. It's been a slow, steady decline ever since.
So why do they die?
I think it comes down to one thing: team size and institutional backing. And I don't just mean the classic "one-man show" problem — though that's very real. Even small volunteer teams of 3, 4, or 5 people carry essentially the same risk. All it takes is a couple of people burning out, getting new jobs, having kids, or simply losing interest — and suddenly the project stalls. No redundancy, no succession plan. The website quietly goes dark and DistroWatch updates the status to "discontinued."
Now before anyone brings up contributor counts — I want to be careful to draw an important distinction here. Package contributors are not the same as distro contributors. AUR maintainers are not Arch developers. Snap package authors are not Canonical engineers — and Snaps run on Fedora, openSUSE, and others anyway, so you can't count those as Ubuntu-specific work regardless. PPAs, Flatpaks, AUR entries — these are ecosystem contributions, not contributions to the distro itself. The actual team maintaining the base system, the kernel integration, the installer, the release engineering — that's almost always a much smaller group than the raw "contributor" numbers suggest. Ubuntu is probably the worst offender for this kind of inflated perception.
What does the real team size picture look like?
I looked this up, and the numbers are telling:
That's not a quantitative difference between the small and large players — it's a qualitative one. Red Hat can lose dozens of key engineers and absorb it without blinking. A 5-person volunteer team loses one or two people and may never recover.
The interesting outliers
Arch is a fascinating case. 26 volunteer developers is a razor-thin team for a distro that serves as the parent to Manjaro, EndeavourOS, Garuda, CachyOS, and many others. However, in September 2024 Valve partnered with Arch developers to support ongoing infrastructure work — almost certainly driven by the Steam Deck's Arch underpinnings. That corporate interest gives Arch a safety net it didn't have before, and probably improves its long-term outlook meaningfully.
Slackware is the paradox. It survived 30+ years on one man's singular vision, which makes it simultaneously the ultimate proof of the rule and the ultimate counterexample. Pat Volkerding deserves enormous respect for what he's built and maintained. But the day he steps back, there's no institutional safety net — and whether the community could carry it forward without him is an open question nobody really wants to test.
Debian remains the model for volunteer-driven sustainability done right. Deep institutional governance, a formal constitution, a democratic leadership structure, and enough contributors that no single departure is catastrophic. If you want to know what a community-run distro looks like when it's built to last, Debian is the answer.
The bottom line
The distros with genuine long-term survival odds are those with either corporate financial backing — Red Hat, Canonical, SUSE — or deep institutional community governance like Debian. Everything else is, to varying degrees, a few key people stepping away from joining that 70% in the graveyard.
None of this is a criticism of the people who build and maintain smaller distros. It's an enormous undertaking and everyone who does it deserves respect, regardless of how long it lasts. But if you're choosing a platform for anything serious — servers, production workloads, long-term desktop stability — the team and funding structure behind it matters as much as the technical merits.
I'm curious what others think. Are there smaller distros you'd consider genuinely sustainable long-term, and what makes them different from the ones that didn't make it?
I've been using Linux since the Yggdrasil and early Slackware days, so I've watched a lot of distros come and go over the decades. I always suspected the attrition rate was bad, but I decided to actually dig into the numbers recently — and they're more sobering than I expected.
According to DistroWatch data analyzed in early 2024, of 958 total distributions ever tracked, only 274 are still active. 637 are officially discontinued, and another 47 are listed as "dormant" — meaning they might come back someday, but don't hold your breath. That's a survival rate of under 30%. Nearly 70% of every Linux distro ever created is dead.
The peak was actually back in 2011, when 323 distros were active simultaneously. It's been a slow, steady decline ever since.
So why do they die?
I think it comes down to one thing: team size and institutional backing. And I don't just mean the classic "one-man show" problem — though that's very real. Even small volunteer teams of 3, 4, or 5 people carry essentially the same risk. All it takes is a couple of people burning out, getting new jobs, having kids, or simply losing interest — and suddenly the project stalls. No redundancy, no succession plan. The website quietly goes dark and DistroWatch updates the status to "discontinued."
Now before anyone brings up contributor counts — I want to be careful to draw an important distinction here. Package contributors are not the same as distro contributors. AUR maintainers are not Arch developers. Snap package authors are not Canonical engineers — and Snaps run on Fedora, openSUSE, and others anyway, so you can't count those as Ubuntu-specific work regardless. PPAs, Flatpaks, AUR entries — these are ecosystem contributions, not contributions to the distro itself. The actual team maintaining the base system, the kernel integration, the installer, the release engineering — that's almost always a much smaller group than the raw "contributor" numbers suggest. Ubuntu is probably the worst offender for this kind of inflated perception.
What does the real team size picture look like?
I looked this up, and the numbers are telling:
- Slackware — essentially one man, Pat Volkerding, maintaining it since 1993. The ultimate one-man show, and honestly a miracle of dedication.
- Arch Linux — 26 named core developers listed on their official developer page. All volunteers. That's the actual distro team, not the AUR community.
- Debian — roughly 1,000 active volunteer developers under community governance. The gold standard for volunteer-driven sustainability.
- Canonical/Ubuntu — approximately 1,200 paid employees as of 2024, though many are in sales, cloud infrastructure, and support rather than distro development specifically.
- Red Hat/RHEL/Fedora — over 19,000 employees globally, backed by IBM's $34 billion acquisition. An entirely different universe.
That's not a quantitative difference between the small and large players — it's a qualitative one. Red Hat can lose dozens of key engineers and absorb it without blinking. A 5-person volunteer team loses one or two people and may never recover.
The interesting outliers
Arch is a fascinating case. 26 volunteer developers is a razor-thin team for a distro that serves as the parent to Manjaro, EndeavourOS, Garuda, CachyOS, and many others. However, in September 2024 Valve partnered with Arch developers to support ongoing infrastructure work — almost certainly driven by the Steam Deck's Arch underpinnings. That corporate interest gives Arch a safety net it didn't have before, and probably improves its long-term outlook meaningfully.
Slackware is the paradox. It survived 30+ years on one man's singular vision, which makes it simultaneously the ultimate proof of the rule and the ultimate counterexample. Pat Volkerding deserves enormous respect for what he's built and maintained. But the day he steps back, there's no institutional safety net — and whether the community could carry it forward without him is an open question nobody really wants to test.
Debian remains the model for volunteer-driven sustainability done right. Deep institutional governance, a formal constitution, a democratic leadership structure, and enough contributors that no single departure is catastrophic. If you want to know what a community-run distro looks like when it's built to last, Debian is the answer.
The bottom line
The distros with genuine long-term survival odds are those with either corporate financial backing — Red Hat, Canonical, SUSE — or deep institutional community governance like Debian. Everything else is, to varying degrees, a few key people stepping away from joining that 70% in the graveyard.
None of this is a criticism of the people who build and maintain smaller distros. It's an enormous undertaking and everyone who does it deserves respect, regardless of how long it lasts. But if you're choosing a platform for anything serious — servers, production workloads, long-term desktop stability — the team and funding structure behind it matters as much as the technical merits.
I'm curious what others think. Are there smaller distros you'd consider genuinely sustainable long-term, and what makes them different from the ones that didn't make it?
