A
PrivateBin
78.3
8,750 stars · license n/a
Self-Hosted
uptime-kuma leads by 19.6 · decisive
A
78.3
8,750 stars · license n/a
B · leads
97.9
94,538 stars · MIT
PrivateBin versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. PrivateBin is written mainly in PHP; uptime-kuma is written mainly in JavaScript. The composite score is 78.3 for PrivateBin and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to PrivateBin's 8,750, a gap of 85,788 (10.80×). Forks are 1,061 for PrivateBin and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 77 versus 100.
Push history: PrivateBin was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 200 for PrivateBin (0.023 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
PrivateBin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for PrivateBin and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both PrivateBin (8,750 stars) and uptime-kuma (94,538 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: PrivateBin is unpriced in this catalog, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against PrivateBin at 78.3, a 19.6 point decisive margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | PrivateBin | uptime-kuma |
|---|---|---|
| GitHub stars | 8,750 | 94,538 |
| Forks | 1,061 | 8,860 |
| Open issues | 200 | 852 |
| Adoption | 79 | 100 |
| Activity | 100 | 100 |
| Community | 77 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.3 | 97.9 |
A minimalist, open source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256 bits AES.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 8,750 for PrivateBin. The gap is 85,788 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both PrivateBin and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
PrivateBin is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.9 and PrivateBin scores 78.3. This page calls that a decisive lead for uptime-kuma.