---
title: "The Observability as Code tools landscape | Grafana Labs"
description: "Where the Foundation SDK and Git Sync fit among Grafana's as-code tools"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Grafana’s Observability as Code tools

Grafana offers several as-code tools. Each solves a different part of the problem, and they can work together. This diagram shows how they relate in a generate-and-sync workflow.

[Diagram showing how Observability as Code tools connect: Foundation SDK generates dashboard JSON, which flows to gcx, Terraform, or Git Sync for use with Grafana](tools-landscape.svg "Diagram showing how Observability as Code tools connect: Foundation SDK generates dashboard JSON, which flows to gcx, Terraform, or Git Sync for use with Grafana")

This journey focuses on the **Foundation SDK** (generate) + **Git Sync** (sync) + **GitHub Actions** (automate) workflow. While the SDK alone only creates dashboards as code but doesn’t update Grafana, Git Sync is what keeps Grafana aligned with the JSON in Git.

## Tool overview

| Tool                   | What it does                                                               | Use it for                                                       | Part of this journey?                                                               |
|------------------------|----------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------|
| **Foundation SDK**     | Defines dashboards in typed code (Go, TypeScript, Python, Java, PHP)       | Generating dashboard JSON programmatically                       | **Yes**                                                                             |
| **Git Sync**           | Syncs dashboard and folder JSON in a Git repo with Grafana                 | Git-native workflows where the repository is the source of truth | **Yes**                                                                             |
| **Terraform provider** | Manages Grafana resources with Terraform plan and apply                    | Teams already using Terraform for infrastructure                 | **No** (covered in the [Terraform journey](/docs/learning-hub/dashboards-as-code/)) |
| **gcx**                | Grafana CLI that pushes or pulls resources from your machine or a pipeline | Quick pushes, scripting, alternate CI deploy steps               | **No**                                                                              |