Software Delivery & Engineering OpsLast reviewed 2026-09-15

GitOps

Git as the single source of truth for declared infrastructure and app state.

Overview

Read the full GitOps guidance

GitOps applies version control discipline to operations: the desired state of infrastructure and applications lives in Git, agents reconcile the real world against it, and every change — human or pipeline — is a pull request with review, history, and rollback. Drift is detected, not debated; recovery is a git revert, not archaeology. OpsRoadmaps assesses GitOps through repository coverage of production state, reconciliation in enforce (not notify) mode, PR-based change flow for infrastructure, and mean time to recover a service from version control alone.

Capabilities

Deployment Automation
One-command, pipeline-driven, auditable releases with progressive rollout.
Rollback Capability
Reverting a bad change in minutes, from version control, without heroics.

Practices

Infrastructure as Code
Production state declared in version control and reconciled automatically.

Tools

Terraform
Declarative infrastructure as code across cloud providers.
Visit site ↗

Architecture patterns

Reference architectures and their trade-offs live in the blueprints library.

Maturity

Maturity for gitops is measured, not guessed — every score traces to your answers. See how maturity is scored.

Put it to work

Assess your GitOps maturity

Turn gaps into a roadmap

Generate a prioritized, effort-aware improvement plan from your results.

Grab the operating checklists

Repeatable checklists for the ceremonies this discipline runs.

Browse the runbooks

Step-by-step responses for when this area catches fire.

DevOps
DevOps is specialized by this area