Contents
gitta Enterprise
The free gitta warns agents on one machine. gitta Enterprise connects agents on every laptop, CI runner and cloud machine in your team, through a server that runs in your own cloud account. Your code never passes through us.
What Enterprise adds
| Feature | Page |
|---|---|
| Warnings between agents on different machines | Team server |
| A team view in the browser | Team server |
| Two or more servers, so one can go down | High availability |
| A token for each person and CI runner, and SSO with your OpenID Connect provider, such as Okta, Entra ID or Google | Tokens and sign-in |
| Each machine's audit events kept on the servers, where nobody on the machine can rewrite them | Audit trail |
| HTTPS, directly or behind your proxy | TLS |
| Seats and renewals | Licence |
| Security warnings between machines when a security control that an agent on one machine weakens, while new code on another machine calls it | Team server |
| Mainframe support for COBOL, copybooks, JCL, mainframe security checks and code pages | Mainframe guide |
| Images for amd64 and arm64 | Docker and containers |
Self-hosted coordination for AI agents
Coordination tools for agents read and change your repositories. Many teams want that software to run where their code already is. gitta Enterprise runs entirely in your own environment.
- The team server runs in your own cloud account, on Kubernetes or on Docker. On premises works the same way.
- The server receives the files an agent changed, never the whole repository. It makes no outbound calls, except to your identity provider for SSO. See Security and data.
- People sign in with SSO through your OpenID Connect provider, such as Okta, Entra ID or Google. Each person and CI runner gets a token that expires and can be revoked. See Tokens and sign-in.
- The
gittacommand is open source, so your security team can read what runs on each machine. Each release has an SBOM and a CBOM. See SBOM and CBOM. - The audit trail of every machine is kept on the servers. See Audit trail.
Where to start
- Read Team server to see how machines report and how warnings come back.
- Deploy the server in your own account with Kubernetes, Google Cloud, AWS or Azure, or Docker.
- Give each person and CI runner a token, or enable SSO. See Tokens and sign-in.
- Connect your repositories with
gitta init --server.
Everything else, including the security checks for the open source languages, is in the free gitta command.