This article explains how to choose among a bare Git server, GitLab, and AngusGit when a team wants to self-host Git on an intranet and replace GitLab. After reading it, you can judge the choice from the features people use every day — code hosting, pull requests, review, issues, and branch protection — and check separately whether pipelines, Git LFS, import scope, and accounts can move over as they are.

When people only push and pull code, a bare Git server is enough. A bare repository stores only Git data and has no working files you can edit. A bare Git server is that kind of repository plus SSH accounts. When you need pull requests and review, and builds can stay on Jenkins, AngusGit Community can replace an intranet GitLab. Built-in pipelines need Team or Enterprise.

1. List what the team uses every day

Before you compare platforms, write down how the team actually uses GitLab today.…