Gitza documentation
Gitza is South Africa’s own Git service, free public and private repositories hosted entirely in South Africa, with data residency as the default for every account and isolated Enterprise instances available on request.
If you have used GitHub, GitLab or Bitbucket, you already know how to use Gitza. The workflow is the one you have now: repositories, branches, pull requests, issues, organisations and teams. What changes is where your code lives. Every layer, from the repositories to the database, file storage and backups, runs on named South African infrastructure, and your clones and pushes stop crossing an ocean.
What you get
- Free public and private repositories from day one. No card, no commitment, no metering.
- Your code at
git.gitza.co.za/you/your-repo, sub-30ms away instead of 150-220ms. - Built-in migration that brings your repositories, issues, pull requests, labels and milestones across from GitHub, GitLab or Bitbucket.
- Organisations and teams, with paid tiers priced per user, in Rands.
- No AI training on your code, ever.
- A signed POPIA operator agreement and your own isolated instance, on Gitza Enterprise.
Where to start
Two ways to run Gitza
Gitza is the shared public service at gitza.co.za . Create an account and push. It is free to start, and Pro and Team add storage, team features and support with response targets.
Gitza Enterprise is your own isolated instance: your own container, database and storage, on your own domain, fully managed, with a signed POPIA operator agreement. It is the same forge with its own walls, priced per instance, on enquiry. See Gitza Enterprise.
Your code stays in South Africa in both.