A
Baserow
81.2
6,354 stars · MIT
Self-Hosted
uptime-kuma leads by 16.7 · decisive
A
81.2
6,354 stars · MIT
B · leads
97.9
94,538 stars · MIT
Baserow 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. Baserow is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 81.2 for Baserow and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to Baserow's 6,354, a gap of 88,184 (14.88×). Forks are 786 for Baserow and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 73 versus 100.
Push history: Baserow 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 1,186 for Baserow (0.187 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both Baserow and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both Baserow (6,354 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: Baserow is freemium, 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 issue health at 50 points (34 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against Baserow at 81.2, a 16.7 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 | Baserow | uptime-kuma |
|---|---|---|
| GitHub stars | 6,354 | 94,538 |
| Forks | 786 | 8,860 |
| Open issues | 1,186 | 852 |
| Adoption | 76 | 100 |
| Activity | 100 | 100 |
| Community | 73 | 100 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 81.2 | 97.9 |
Baserow is an open, self-hostable database and grid tool in the Airtable mold. It stores structured data with views and an API you can run yourself.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 6,354 for Baserow. The gap is 88,184 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Baserow and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
Baserow 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. 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 Baserow scores 81.2. This page calls that a decisive lead for uptime-kuma.