The State of Self-Hosted Software 2026

We measure the maintenance health of every project in the self-hosted catalogue, every week. This is what 1362 projects look like in aggregate — which categories are thriving, which runtimes age worst, and how much of the ecosystem has quietly stopped moving.

Data as of 2026-11-20 · 1136 projects scored · 226 not measurable · method · Free to cite and reproduce with attribution.

29%
slowing or at risk
17%
impossible to measure
71%
released in last 90 days
7%
no commit last quarter
64
median health score

The headline

29% of scored self-hosted projects are slowing or at risk — 325 of 1136. That is the figure worth carrying away: pick a project at random from a directory and there is roughly a one-in-three chance its development has materially decelerated or stopped.

It is not all decay, and the ecosystem's reputation for abandonment is unfair. 71% shipped a tagged release within the last ninety days, and only 7% went the whole quarter without a single commit. Self-hosted software is not dying — it is bimodal. A large active core ships constantly, a long tail sits untouched, and the median score of 64 falls in the valley between them.

Which is precisely why an average is useless here and a per-project score is not. The catalogue does not have a health problem; it has a selection problem. The good options and the dead ones sit side by side in every category, indistinguishable until you look at the commit log — and star counts actively mislead, because they only ever go up.

Distribution of health scores

BandScoreProjectsShare
Thriving 82–100 212 19%
Healthy 68–81 291 26%
Steady 52–67 308 27%
Slowing 36–51 193 17%
At risk 0–35 132 12%

The measurement gap nobody talks about

226 of 1362 projects (17%) cannot be scored at all, because they are developed outside GitHub — on Codeberg, on self-hosted Forgejo or GitLab, or on infrastructure the project runs itself.

There is something quietly appropriate about that: the self-hosting community hosts its own forges, and in doing so becomes invisible to the tooling that measures open-source health. Every ecosystem dashboard you have ever read has this blind spot, and almost none of them say so. We report those projects as unrated rather than guessing, because scoring them from missing data produces exactly one outcome — healthy projects labelled dead.

Healthiest categories

Median health score, categories with at least 8 scored projects.

Categories in trouble

The same measure, at the other end. A low median does not mean no good option exists — it means most of the field has stopped moving, so picking at random is risky.

Which runtimes age best

Median health by the language or platform a project is built on, minimum 15 scored projects. This says more about which communities are currently active than about the languages themselves.

PlatformProjectsMedian
K8S 74 76
deb 82 74
Java 56 71
Nodejs 194 68
C++ 35 67
Python 137 67
Docker 711 66
C# 16 65
Ruby 32 65
Rust 39 64
Go 138 63
PHP 197 63
Shell 20 58
C 31 55
Javascript 18 26

Licences

The ten most common licences in the catalogue, with the median health of the projects using them.

LicenceProjectsShareMedian health
MIT MIT License 369 27% 61
AGPL-3.0 GNU Affero General Public License 3.0 319 23% 67
GPL-3.0 GNU General Public License 3.0 233 17% 60
Apache-2.0 Apache, Version 2.0 144 11% 69
GPL-2.0 GNU General Public License 2.0 108 8% 63
⊘ Proprietary ⊘ Proprietary 70 5% 74
BSD-3-Clause BSD 3-Clause "New" or "Revised" 38 3% 55
MPL-2.0 Mozilla Public License 18 1% 70

The busiest repositories

Raw commit volume over 11 months. Volume is not quality — but it does show where the ecosystem's engineering effort is actually going.

#ProjectCommitsStarsHealth
1 PostHog 41k 41k Thriving · 99
2 Wekan 25k 21k Thriving · 98
3 Agenta 21k 4.9k Thriving · 93
4 Home Assistant 21k 92k Thriving · 100
5 TriliumNext Notes 19k 39k Thriving · 99
6 Sentry Self-Hosted 19k 46k Thriving · 96
7 OpenProject 18k 18k Thriving · 97
8 Ente 18k 30k Thriving · 98
9 Appwrite 17k 58k Thriving · 99
10 Infisical Community Edition 14k 31k Thriving · 95
11 ElasticSearch 14k 79k Thriving · 96
12 One Time Secret 14k 3k Thriving · 91
13 Weblate 13k 6.2k Thriving · 91
14 Budibase 13k 28k Thriving · 91
15 ZenTao 11k 1.7k Thriving · 85

Accelerating

Commit activity up sharply last quarter versus the one before.

Dreeve 1 → 989
Relaticle 18 → 2887
LibreTime 1 → 115
PixelFed 41 → 3743
Wiki.js 3 → 266
PKVault 2 → 163
Fluxer 59 → 2832
TinyFeed 1 → 34
Movary 21 → 652
Snapcast 1 → 28

Popular but stalling

Well-known projects with little recent activity — the trap star counts hide.

Seafile ★ 15k 39 commits
Automatisch ★ 14k 5 commits
A Dark Room ★ 8.4k 0 commits
Sandstorm ★ 7.1k 9 commits
Outline Server ★ 6.3k 16 commits
Tiny File Manager ★ 6k 21 commits
Pinchflat ★ 5.5k 3 commits
Restreamer ★ 5.2k 2 commits
Colanode ★ 5.2k 39 commits
musikcube ★ 4.9k 1 commits

Method, in one paragraph

Every project is scored 0–100 from public repository metadata: commit volume over 11 complete months (40 points, percentile-ranked against the whole catalogue), days since the last tagged release (25, absolute), community size (20, percentile-ranked) and quarter-on-quarter momentum (15, absolute). Percentile ranking on the two continuous components stops the scale saturating and makes the score impossible to inflate with trivial commits. Archived and unmeasurable projects are excluded from the ranking base. Full method, including its known limitations.

Using these figures

Every number here is recomputed from source on each rebuild, so this page does not go stale the way an annual PDF does. You are welcome to quote, chart or reproduce any of it — a link back to this page is all we ask. The underlying software metadata comes from the community-maintained awesome-selfhosted dataset under CC-BY-SA 3.0 (attribution); the scores and analysis are ours.

Last recomputed 2026-11-20 from source data dated 2026-11-20.