> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-gitops/get-started/gitops-vs-gitex-vs-config.md).

# Harness GitOps vs Harness Git Experience vs Config as Code

This topic describes key differences between Harness GitOps, Harness Git Experience and Config as Code

Harness has multiple Git-based features, and it is important to understand the differences:

* **Harness GitOps:** Manages infrastructure and service deployments by syncing the desired state from Git to the live cluster state. Changes in the source manifest repo automatically trigger synchronization, enabling both cluster bootstrapping and full-service deployments. Go to [Harness GitOps Basics](/continuous-delivery/use-gitops/get-started/harness-git-ops-basics.md) to learn more about Harness GitOps.
* **Config-as-Code:** Harness supports full YAML-based configuration of pipelines and other Harness entities. Harness Pipeline Studio provides an integrated YAML editor with hints and autocomplete for defining and managing configurations. Go to [Create a pipeline](https://developer.harness.io/docs/platform/pipelines/create-pipeline-quickstart) to learn more about YAML-based pipeline configuration.
* **Harness Git Experience:** Synchronizes pipelines and other entities with Git repositories, allowing changes to be managed directly in Git or through the Harness Manager UI. Go to [Harness Git Experience overview](https://developer.harness.io/docs/platform/git-experience/git-experience-overview) to learn more about Harness Git Experience.

{% @harness-feedback/feedback %}