---
title: "Signature levels | Grafana Labs"
description: "How public and private plugins are signed, and the signature levels Grafana uses"
---

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

# Signature levels

Every plugin is signed under a **signature level**, which determines how the plugin can be distributed. How you get that level depends on whether your plugin is public or private.

## Public plugins are reviewed first

Grafana reviews public plugins before you can sign them. If your plugin is approved, Grafana assigns it one of these levels:

- **Community**: Community plugins have dependent technologies that are open source and not for profit. They’re published in the Grafana plugin catalog, and you can sign them free of charge.
- **Commercial**: Commercial plugins are tied to a paid product or offered by a for-profit business, or have dependent technologies that are closed source or commercially backed. They’re published in the Grafana plugin catalog, and signing them requires a Commercial Plugin Subscription.

Plugins sold through the Grafana Marketplace have their own **Marketplace** level. You learn about it in the next section.

## Private plugins aren’t reviewed

**Private** plugins are for use on your own Grafana instances. They can’t be distributed to the Grafana community or to your customers, and they aren’t published in the Grafana plugin catalog. You sign a private plugin yourself, without a review, for the Grafana instance URLs you list when you sign it.

Private plugins aren’t compatible with Grafana Cloud.

Refer to [Plugin signatures](https://grafana.com/docs/grafana/latest/administration/plugin-management/plugin-sign/) and the [Grafana plugins policy](https://grafana.com/legal/plugins/) for more details.
