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
Docs

For your role

What gittan means for how you work — depending on what you do.

Dev teams

Own your code, your pipeline, and your deployments. No one else approves your work.

Platform engineers

Org-wide policies, centralized security, deployment hooks — everything organized per team from the start.

Engineering leaders

Team metrics, org changelog, research-backed principles, and a clear view of what shipped.