Skip to content
DevUtils Online

Self-Hosted

microsandbox vs uptime-kuma

uptime-kuma leads by 12.7 · clear

microsandbox 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. microsandbox is written mainly in Rust; uptime-kuma is written mainly in JavaScript. The composite score is 85.2 for microsandbox and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to microsandbox's 9,108, a gap of 85,430 (10.38×). Forks are 526 for microsandbox and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 69 versus 100.

Push history: microsandbox 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 195 for microsandbox (0.021 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

microsandbox is listed as Apache-2.0, 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. 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 96 for microsandbox and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both microsandbox (9,108 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: microsandbox is open source, uptime-kuma is open source.

uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 31 points (69 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against microsandbox at 85.2, a 12.7 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

microsandbox versus uptime-kuma metrics
Signal microsandbox uptime-kuma
GitHub stars 9,108 94,538
Forks 526 8,860
Open issues 195 852
Adoption 80 100
Activity 100 100
Community 69 100
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 85.2 97.9

Questions this page answers

Which has more GitHub stars, microsandbox or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 9,108 for microsandbox. The gap is 85,430 stars.

Which was updated more recently, microsandbox or uptime-kuma?

Both were last pushed on 17 November 2026.

Can I self-host both microsandbox and uptime-kuma?

Yes. This catalog marks both microsandbox and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, microsandbox or uptime-kuma?

microsandbox is listed as Apache-2.0, 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. 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.

Who wins the microsandbox vs uptime-kuma score?

uptime-kuma scores 97.9 and microsandbox scores 85.2. This page calls that a clear lead for uptime-kuma.

Related comparisons