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.
- MIT
- Go
- Docker
- Actively maintained
Project Management comparison
Pick Gitea for built-in CI, a package registry and a busier development pace; pick Gogs only if you want the simplest possible Git server with the smallest feature set.
Both are open source and run on your own server. Below: a side-by-side of license, stack and features, live GitHub activity, and our verdict on who should pick which.
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.
Painless self-hosted Git Service written in Go.
Head-to-head
Hand-checked differences first, then live numbers from GitHub, refreshed with every catalog update.
| Aspect | ||
|---|---|---|
| License | MIT. | MIT. |
| History | Community fork of Gogs created in 2016 to allow more maintainers and faster development. | The original project, still led by a small core team. |
| CI/CD | Built-in Gitea Actions, compatible with most GitHub Actions workflows. | No built-in CI; integrates with external tools such as Jenkins through webhooks. |
| Package registry | Built-in registry for Docker, npm, PyPI, Maven, Cargo and many more formats. | No package registry. |
| Database | PostgreSQL, MySQL, MariaDB, MSSQL or SQLite. | PostgreSQL, MySQL, MariaDB or SQLite. |
| Hardware needs | Light: a Raspberry Pi or small VPS is enough for small teams. | Very light: the README cites 2 CPU cores and 512 MB RAM as a team baseline. |
| GitHub stars | 58,319 | 47,859 |
| Commits, last 12 months | 1,696 | 225 |
| Last commit | Oct 6, 2026 | Sep 12, 2026 |
| Latest release | v28.0.0Sep 29, 2026 | v0.14.3Jun 7, 2026 |
| Main language | Go | Go |
| Official Docker image | Yes | Yes |
| Repository | go-gitea/gitea | gogs/gogs |
Swipe the table sideways to see both apps. GitHub figures come from the public API. Highlighted values are the higher of the two.
Gitea started as a fork of Gogs in 2016 and has since added Actions CI, a multi-format package registry, project boards and many integrations, so it is the better default for almost everyone. Gogs remains a reasonable pick for a minimal personal Git server where fewer features means less to maintain.
Best for
Teams that want repos, CI and packages in one lightweight server.
Best for
Minimal personal Git hosting with the fewest moving parts.
Not sure yet? Spin up a small VPS or a managed instance, try both for a week, and keep the one that fits.
Sponsored links: we may earn a commission if you sign up, at no extra cost to you. It never affects rankings.
Yes. Gitea was forked from Gogs in 2016 by contributors who wanted a community-driven governance model, and the two projects have diverged significantly since.
Gitea historically supported migrating a Gogs installation, but the path depends on your Gogs version. The simplest reliable route is to use Gitea's repository migration tool to import each repository with its issues.
Not natively. Gogs sends webhooks that external CI systems can consume, while Gitea ships its own Actions runner system.
Gitea has 58,319 GitHub stars against 47,859 for Gogs. Over the last twelve months Gitea received 1,696 commits and Gogs received 225, so Gitea is the more actively developed of the two right now. Stars measure interest, not fit, so weigh them against the differences above.