Gitea

Gitea is a self-hosted Git service under the MIT license with code review, CI/CD and a package registry, plus paid Enterprise and Cloud editions from CommitGo.

Gitea gives a development team its own Git server, with code review, issue tracking, CI/CD and packages in one service it installs and controls. The project is open source, and CommitGo, Inc., founded by members of the project's Technical Oversight Committee, provides its leadership and commercial support. Code stays on infrastructure the team chooses rather than on a host it does not run. Pull requests let reviewers leave comments, request changes or approve, and protected branches can require a set number of approvals before a merge. A code owners file requests reviews automatically when matching files change. Gitea Actions is the built-in CI/CD, running workflows stored in the repository on runners the team registers. The package registry holds container images beside npm, Maven, PyPI and NuGet packages. Gitea Enterprise adds SAML single sign-on, audit logs, Kubernetes autoscaling runners, dependency scanning and secret push protection. Gitea suits engineering teams that want source code on their own servers, and companies whose security rules call for single sign-on and an audit history on that server. It also fits teams leaving GitHub, GitLab or Gogs who want a familiar pull request workflow. Three editions are on offer: the open-source download, Enterprise for self-managed instances with SLA-backed support, and Gitea Cloud, where CommitGo runs the instance and its runners. Open source projects can host on gitea.com without running a server. A move from GitHub starts in the migration form, which brings a repository's issues and pull requests across with its history. From there, workflow files drive Gitea Actions on the team's own runners, or on managed runners in Gitea Cloud with the provider and region the customer picks. Developers sign in through an OAuth2 provider or, on Enterprise, through the SAML identity provider the company already uses. Builds end in the package registry, where images and libraries follow the same team permissions as the code they came from.