Desired state in Git
The system described in files a team reviews.
DevOps
GitOps services measured against the four principles
We have no published GitOps build. We have shipped Docker Compose deployments and Azure DevOps pipelines, and we check them against the four OpenGitOps principles.
0Published builds on GitOps
4OpenGitOps principles
v1.0.0Version of the principles
3Delivery builds nearby
What we build
What we would take on with GitOps
Agents that pull
Agents that pull the desired state from Git, with the pipeline ending at the build.
Continuous reconciliation
Drift between Git and the running system found and corrected.
History you can audit
Every release is a commit with a full version history.
Architecture
Where GitOps would sit
A GitOps agent between Git and the system
Source
Git repositoryDesired state
Agent
GitOps agentWhere it would sit
Run
Docker ComposeTruckFleet Labs
AzureHydrajaws, Verify Auto
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
Principles
The four GitOps principles
OpenGitOps principles, version 1.0.0
DeclarativeThe desired state is expressed declaratively.
Versioned and immutableDesired state is stored with immutability and a complete version history.
Pulled automaticallySoftware agents pull the desired state from the source.
Continuously reconciledAgents observe the actual state and try to apply the desired state.
Source: OpenGitOps, opengitops.dev, GitOps Principles v1.0.0, checked 5 November 2026.
Builds
The closest builds we can show you
Logistics, fleet operations
TruckFleet Labs
A Docker multi-stage build with Docker Compose behind a FastAPI back end.
38Drivers on the app by week three
Construction safety testing, United Kingdom
Hydrajaws Limited
Azure DevOps pipelines and environments rebuilt for stable releases.
500%Surge in potential clients
Fintech, Hong Kong
Cryptocurrency marketing platform
Daily CI/CD deployments on a Kanban workflow.
30,000+Concurrent users the platform had to support
Fit check
When GitOps is the right call
Pick GitOps when
- You run several environments that drift
- You want every release reviewed as a commit
- Your system runs on Kubernetes or another declarative platform
Look elsewhere when
- You need a published GitOps build to inspect, which we do not have
- A few services on one host, where Docker Compose is enough
- No one on your team will own the repository
Explore
Same job, other tools
Where we used it
Stack
What GitOps usually sits beside
KubernetesDocker
TerraformAzure
AWS
JenkinsFAQs
What buyers ask first
What are the GitOps principles?
Four: the desired state is declarative, versioned and immutable, pulled automatically by software agents, and continuously reconciled with the actual state. OpenGitOps publishes them as version 1.0.0.
Do you have a published GitOps build?
No. We say so on the first call and show the nearest work, which is Docker Compose deployments and Azure DevOps pipelines.
Is GitOps the same as CI/CD?
No. GitOps is a set of principles for operating a system. A pipeline can build the change, and an agent that pulls and reconciles the desired state delivers it.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us how a change reaches production
Thirty minutes on your repositories, your environments and your release steps. No sales pitch.