Your code never leaves your company.
gitta Enterprise runs as a small server in your own cloud account, your Kubernetes cluster or your own data centre. It receives only the files an agent changed, never the whole repository, it calls out only to your sign-in provider, and it sends your code to no AI model. Run it fully offline and it keeps working.
What crosses your perimeter.
The boundary is simple on purpose, so your security team can draw it on one page.
Stays inside
- Your source code and your repositories
- Your tests, run on the combined work
- The gitta server and every audit record
- The files an agent changed
Leaves the boundary
- A sign-in check to your own OpenID Connect provider
That is the whole list. No source, no diffs and no telemetry are sent anywhere, and nothing goes to an AI model. Your code and every audit record stay in your account and region.
Runs where your code already runs.
The same small server, on the platform your team operates today.
KubernetesEKS, GKE, AKS and your own
AWSyour account
Google Cloudyour project
Azureyour subscription- Dockerany container host
- Your data centrefully offline
A server built to be signed off.
Small, closed and verifiable, so the people who own security can say yes.
- One locked-down process
- A single program in a small container, with no shell, running without root rights on a read-only file system.
- Your company sign-in, with SCIM
- People and CI runners sign in with your OpenID Connect provider, such as Okta, Entra ID or Google, with SCIM 2.0 provisioning, so disabling a person ends their tokens and sessions at once.
- Your own TLS and certificate authority
- gitta serves over HTTPS, directly or behind your proxy, with your own private certificate authority.
- High availability across zones
- Run gitta in high availability, with two or three servers in different zones. When one is down, the others still answer.
- Software you can read
- The gitta command is open source, and each release lists its parts and every algorithm and key it uses.
- An immutable record
- Each machine’s changes are kept on the servers as a hash-chained trail, out of reach of anyone on that machine.
Run gitta inside your own walls.
Tell us where your code lives and how your team signs in, and we will help you plan the deployment in your own infrastructure. See the Enterprise overview and agent governance.
