Skip to content
DevUtils Online

DevOps

Gitea vs oneuptime

Gitea leads by 27.2 · decisive

A · leads

Gitea

96.5

59,134 stars · MIT

B

oneuptime

69.3

7,826 stars · license n/a

Gitea versus oneuptime is a DevOps comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Gitea is written mainly in Go; oneuptime is written mainly in TypeScript. The composite score is 96.5 for Gitea and 69.3 for oneuptime.

Gitea has 59,134 GitHub stars to oneuptime's 7,826, a gap of 51,308 (7.56×). Forks are 7,414 for Gitea and 495 for oneuptime. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 70.

Push history: Gitea was last pushed on 17 November 2026 (0 days ago), and oneuptime was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,172 for Gitea (0.037 per star) and 1,124 for oneuptime (0.144 per star). Issue-health scores are 70 and 34; activity scores are 100 and 100.

Gitea 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. oneuptime 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. License scores in this pair are 96 for Gitea and 30 for oneuptime. This is a procurement signal, not legal advice.

Only Gitea is marked self-hostable here (59,134 stars, deploy score 100). oneuptime is not (7,826 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: Gitea is open source, oneuptime is unpriced in this catalog.

Gitea is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).

Gitea finishes ahead at 96.5 against oneuptime at 69.3, a 27.2 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.

Gitea versus oneuptime metrics
Signal Gitea oneuptime
GitHub stars 59,134 7,826
Forks 7,414 495
Open issues 2,172 1,124
Adoption 100 82
Activity 100 100
Community 100 70
Issue health 70 34
License 96 30
Self-hosting 100 35
Composite 96.5 69.3

Gitea

Gitea is a lightweight self-hosted Git service with issues, pull requests, and actions. It is the usual choice when a team wants a small forge they can run themselves.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Gitea or oneuptime?

Gitea has more GitHub stars: 59,134 versus 7,826 for oneuptime. The gap is 51,308 stars.

Which was updated more recently, Gitea or oneuptime?

Both were last pushed on 17 November 2026.

Can I self-host both Gitea and oneuptime?

Only Gitea is marked self-hostable. oneuptime is not.

Which license is easier to embed in a commercial product, Gitea or oneuptime?

Gitea 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. oneuptime 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Gitea vs oneuptime score?

Gitea scores 96.5 and oneuptime scores 69.3. This page calls that a decisive lead for Gitea.

Related comparisons