---
title: "Before you begin | Grafana Labs"
description: "What you need on your machine to build, and what you only need to publish"
---

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

# Before you begin

To build and run a plugin locally, you need:

- Node.js and a package manager, for every plugin type.
- Docker, which runs the local Grafana instance you’ll test against.
- Go and Mage, but only if your plugin has a **backend component**.
- Optionally, an AI coding assistant, if you choose to build your plugin with AI.

## Do I need an org?

You need a Grafana Cloud organization where you have the Admin role **only** if you want to publish a plugin.

The `create-plugin` tool asks for your Grafana Cloud organization name early on and uses it as the first part of your plugin’s ID. You can generate, build, and run a plugin locally with a placeholder name, but signing only works when the plugin ID starts with your real organization name. If you plan to publish, enter your real Grafana Cloud organization name from the start so you don’t have to rename your plugin later.

Even if you don’t have the Admin role in your organization, complete the learning journey to fully understand the plugin development and publishing cycle.
