Need advice about which tool to choose?Ask the StackShare community!
Gitea vs GitHub Enterprise: What are the differences?
Developers describe Gitea as "A painless self-hosted Git service". Gitea is a community managed lightweight code hosting solution written in Go. It published under the MIT license. On the other hand, GitHub Enterprise is detailed as "The on-premises version of GitHub, which you can deploy and manage in your own, secure environment". GitHub Enterprise lets developers use the tools they love across the development process with support for popular IDEs, continuous integration tools, and hundreds of third party apps and services.
Gitea and GitHub Enterprise can be categorized as "Code Collaboration & Version Control" tools.
Gitea is an open source tool with 14.4K GitHub stars and 1.56K GitHub forks. Here's a link to Gitea's open source repository on GitHub.
DuckDuckGo, Shutterstock, and OkCupid are some of the popular companies that use GitHub Enterprise, whereas Gitea is used by osu! Ripple, LunchBadger, and PlayNet. GitHub Enterprise has a broader approval, being mentioned in 38 company stacks & 46 developers stacks; compared to Gitea, which is listed in 8 company stacks and 10 developer stacks.
We are using a Bitbucket server, and due to migration efforts and new Atlassian community license changes, we need to move to a new self-hosted solution. The new data-center license for Atlassian, available in February, will be community provisioned (free). Along with that community license, other technologies will be coming with it (Crucible, Confluence, and Jira). Is there value in a paid-for license to get the GitHub Enterprise? Are the tools that come with it worth the cost?
I know it is about $20 per 10 seats, and we have about 300 users. Have other convertees to Microsoft's tools found it easy to do a migration? Is the toolset that much more beneficial to the free suite that one can get from Atlassian?
So far, free seems to be the winner, and the familiarization with Atlassian implementation and maintenance is understood. Going to GitHub, are there any distinct challenges to be found or any perks to be attained?
These are pretty competitive, and to recommend one over the other would require understanding your usage. Also, what other tools you use: for instance, what do you use for Issue-tracking, or for build pipelines. In your case, since you are already using Bitbucket, the question would be: do you have any current pain-points? And, on the other hand, do you already use Atlassian's JIRA, where you'd benefit from the tight integration? So, though I would not recommend one over the other just in general,. But, if Bitbucket fulfills your current use-cases, then there seems to be little motivation to move.
Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.
Pros of Gitea
- Self-hosted22
- Lightweight15
- Free14
- Simple11
- Multiple code maintainers9
- Easy Setup8
- Pull requests and code reviews6
- Written in Go5
- Squash and Merge is supported5
- Import existing git repositories5
- Nice gui4
- Run in Raspberry Pi3
- Community-fork of Gogs2
- LDAP Support2
Pros of GitHub Enterprise
- Expensive - $$$3
- Code security2
- CDCI with Github Actions2
- Both Cloud and Enterprise Server Versions available1
- Draft Pull Request1
- User experience0
Sign up to add or upvote prosMake informed product decisions
Cons of Gitea
- Community-fork of Gogs3
- Easy Windows authentication is not supported0
Cons of GitHub Enterprise
- $$$2
