gittan for engineering leaders
Team metrics per team, research-backed flow, and a clear view of security posture.
From commit to production, nothing in between
Push, pipeline passes, deployed. Every commit is gated — the pipeline runs before it lands. The team owns the code, the pipeline enforces quality, deployment is immediate.
The pipeline runs every check your org requires — tests, type checks, security scans, compliance policies. Every time, on every push, no exceptions. The speed comes from removing the waiting, not the verification.
Built on research, not convention
Small batches, team ownership, trunk-based development, automated gating — these come from the DORA research program and the Accelerate book. Decades of data show that high-performing teams deploy more often, fail less, and recover faster. gittan makes that the default.
What creates software quality →Team metrics
Push frequency, pipeline lead time, rejection rate, recovery time — measured per team, automatically. Inspired by DORA, adapted for gated push: two metrics map directly to DORA, two measure the gate instead of production. gittan runs every pipeline, so the data is there without instrumentation.
Which teams push daily and which push monthly. Where pipelines fail often and where they rarely do. Which repos are active and which are dormant. You see it because the platform sees it — nobody reports upward.
Team metrics →Security posture per team
Every team has a security view showing open vulnerabilities across their repos — what needs fixing and how critical it is. As a leader, you see active findings per team and which teams need attention.
Security scanning is an org-level policy. Teams cannot disable it. Consistent coverage without chasing individual repos.
Per-org pricing
Per org, not per seat. Add developers, contractors, or temporary team members without recalculating license costs. CI usage beyond the included minutes is added as capacity blocks — predictable, capped, no surprises. See how it compares to GitHub and Bitbucket →