gittan.
How it worksPricingDocs Sign in

Why gittan

How we think

For your role

Dev teamsPlatform engineersEngineering leaders

Getting started

OverviewCreate your orgFirst pushTeams & reposYour first pipelineImport reposPublic repos & packagesDevice authorizationFrom GitHub Actions

Pipelines

OverviewConfigurationPoliciesShared stepsBase imagesImage pinningDeploy hooksPipeline previewDeploy feedbackExamples

Teams & metrics

OverviewTeam metricsCode reviewChangelogDependenciesNotifications

Security

OverviewPeopleMachines & tokensPipeline identitySupply chainAudit logSecurity findingsChange managementGroup sync

Reference

CLIPipeline YAMLPolicy YAML

Teams & metrics

Teams are the unit of ownership in gittan. Every repo belongs to a team. Every metric is per team. There are no personal namespaces.

Team metrics

Push-cycle metrics per team, inspired by DORA. Push frequency, lead time, rejection rate, recovery time.

Code review

Inline comments on branch diffs. No pull requests — review happens on the branch itself.

Dependency graph

See which repos depend on each other, and trigger downstream pipelines when an upstream changes.

Org changelog

An AI-generated summary of what changed across your org, every day.

Notifications

Pipeline results delivered to your team's Slack channel.