---
title: "Deployment options | Grafana Labs"
description: "Choosing the right deployment method for your workflow"
---

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

## Deploy your dashboards

Now it’s time to connect your code-generated dashboards to a running Grafana instance.

## Deployment methods available in Grafana

Grafana supports several ways to deploy dashboards from code. The right choice depends on the workflow your team already uses. Each has different trade-offs.

| Method          | How it works                                                                                                      | Best for                                | Trade-off                                         |
|-----------------|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------|---------------------------------------------------|
| **Terraform**   | Define dashboards in HCL files and deploy them with the same plan-and-apply workflow as your other infrastructure | Teams with existing Terraform workflows | Another tool to learn if you don’t already use it |
| **Git Sync**    | Store dashboard JSON in a GitHub repository; Grafana automatically synchronizes it                                | Git-native teams, no custom pipelines   | Less control over the deployment process          |
| **Grafana API** | Send HTTP requests to Grafana directly; the other two methods are built on top of it                              | Full custom control                     | More code to write and maintain                   |

**This journey covers Terraform deployments.** You’ll produce as-code workflows that integrate with your existing infrastructure code.