Skip to content
DevUtils Online

Self-Hosted

airbyte vs uptime-kuma

uptime-kuma leads by 17.9 · decisive

A

airbyte

80.0

22,403 stars · license n/a

airbyte 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. airbyte is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 80.0 for airbyte and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to airbyte's 22,403, a gap of 72,135 (4.22×). Forks are 5,539 for airbyte and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 95 versus 100.

Push history: airbyte 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 2,839 for airbyte (0.127 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.

airbyte 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 airbyte and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both airbyte (22,403 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: airbyte 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 airbyte at 80.0, a 17.9 point decisive 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.

airbyte versus uptime-kuma metrics
Signal airbyte uptime-kuma
GitHub stars 22,403 94,538
Forks 5,539 8,860
Open issues 2,839 852
Adoption 87 100
Activity 100 100
Community 95 100
Issue health 34 84
License 30 96
Self-hosting 100 100
Composite 80.0 97.9

airbyte

Open-source data movement for ELT pipelines and AI agents — from APIs, databases & files to warehouses, lakes, and AI applications. Both self-hosted and Cloud.

Project site · GitHub · Full profile

Questions this page answers

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

uptime-kuma has more GitHub stars: 94,538 versus 22,403 for airbyte. The gap is 72,135 stars.

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

Both were last pushed on 17 November 2026.

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

Yes. This catalog marks both airbyte 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, airbyte or uptime-kuma?

airbyte 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.

Who wins the airbyte vs uptime-kuma score?

uptime-kuma scores 97.9 and airbyte scores 80.0. This page calls that a decisive lead for uptime-kuma.

Related comparisons