Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD.

Thriving · 91
91/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 35/40
Releases 25/25
Community 20/20
Momentum 12/15

Commit activity more than 87% of tracked projects; popularity more than 98%. How this is calculated.

Commits, last 11 months

2025-10: 89 commits 2025-11: 68 commits 2025-12: 102 commits 2026-01: 95 commits 2026-02: 134 commits 2026-03: 132 commits 2026-04: 185 commits 2026-05: 201 commits 2026-06: 171 commits 2026-07: 211 commits 2026-08: 226 commits
2025-10 1614 total 2026-08
Stars58k
Latest releasev1.27.3 · 29 Aug 2026
Repo updated28 Sept 2026
LicenceMIT
Built withGo, Docker, K8S

Is Gitea actively maintained?

Development is ongoing. The repository recorded 1614 commits over the same window, and the last three months alone account for 608 of them.

The most recent tagged release, v1.27.3, shipped within the last month — a current, installable version exists today.

Of the 45 projects we track in Software Development - Project Management, Gitea ranks #2 by health score — in the top quarter of its category.

What Gitea actually does

Gitea is a self-hosted software development service that combines Git repositories, code review tools, and team collaboration spaces into a single platform. It also includes package registries and continuous integration capabilities to handle the complete application lifecycle. Written in Go, it functions as a lightweight alternative to larger platforms like GitHub or GitLab.

Best fit: Teams and individuals who want a complete, self-hosted code management and collaboration platform without the resource demands of heavier enterprise alternatives.

Worth knowing: It requires significant ongoing management for upgrades, backups, and user access control, and it overlaps heavily with more established self-hosted Git solutions.

Deployment notes

Deployment typically involves setting up persistent storage for your repository data, configuring a separate database such as PostgreSQL or MySQL, and placing the container behind a reverse proxy to handle TLS termination.


Gitea as a replacement for


Alternatives to Gitea

Projects in the same categories, ordered by health score.