<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Publish to the Grafana plugin catalog on Grafana Labs</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/</link><description>Recent content in Publish to the Grafana plugin catalog on Grafana Labs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/docs/learning-hub/plugin-development/03-publish-to-the-catalog/index.xml" rel="self" type="application/rss+xml"/><item><title>What is the Grafana plugin catalog, and why publish?</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/01-what-publishing-gets-you/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/01-what-publishing-gets-you/</guid><content><![CDATA[&lt;h1 id=&#34;what-the-grafana-plugin-catalog-is-and-why-publish&#34;&gt;What the Grafana plugin catalog is, and why publish&lt;/h1&gt;
&lt;p&gt;The &lt;strong&gt;Grafana plugin catalog&lt;/strong&gt; at &lt;a href=&#34;/plugins&#34;&gt;grafana.com/plugins&lt;/a&gt; is where Grafana users find and install plugins. Listing your plugin there is free of charge.&lt;/p&gt;
&lt;h2 id=&#34;your-plugin-needs-a-signature-to-run-outside-development&#34;&gt;Your plugin needs a signature to run outside development&lt;/h2&gt;
&lt;p&gt;Your plugin runs in your local Grafana because the development environment allows unsigned plugins. Outside of development, Grafana doesn&amp;rsquo;t load a plugin unless it&amp;rsquo;s signed.&lt;/p&gt;
&lt;p&gt;Grafana Cloud doesn&amp;rsquo;t support unsigned plugins at all. For your plugin to be available in Grafana Cloud, it needs a Community or Commercial signature, and you only get one of those by submitting your plugin for review.&lt;/p&gt;
&lt;h2 id=&#34;other-people-can-find-and-install-it&#34;&gt;Other people can find and install it&lt;/h2&gt;
&lt;p&gt;After your plugin is published, it appears in the Grafana plugin catalog alongside the plugins from Grafana Labs and the community, where millions of Grafana users can discover it. Users can install it directly, including from inside their own Grafana instance.&lt;/p&gt;
]]></content><description>&lt;h1 id="what-the-grafana-plugin-catalog-is-and-why-publish">What the Grafana plugin catalog is, and why publish&lt;/h1>
&lt;p>The &lt;strong>Grafana plugin catalog&lt;/strong> at &lt;a href="/plugins">grafana.com/plugins&lt;/a> is where Grafana users find and install plugins. Listing your plugin there is free of charge.&lt;/p></description></item><item><title>The publishing workflow</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/02-publishing-workflow/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/02-publishing-workflow/</guid><content><![CDATA[&lt;h1 id=&#34;the-publishing-workflow&#34;&gt;The publishing workflow&lt;/h1&gt;
&lt;p&gt;Follow this order to submit your plugin:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Package the plugin, but don&amp;rsquo;t sign it yet.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Optionally, add a ready-to-run test setup for reviewers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Run the plugin validator, a tool you run yourself to catch problems before you submit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Submit the plugin:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;In Grafana Cloud, go to &lt;strong&gt;Org Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;My Plugins&lt;/strong&gt; and click &lt;strong&gt;Submit New Plugin&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;You must have the Admin role in the organization.&lt;/li&gt;
&lt;li&gt;The submission form asks for a public URL to your packaged plugin&amp;rsquo;s ZIP file, for example attached to a release in your Git repository, along with the file&amp;rsquo;s SHA1 hash and a URL to your plugin&amp;rsquo;s source code. Refer to &lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/publish-a-plugin&#34;&gt;Publish or update a plugin&lt;/a&gt; for all the fields in the form.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Wait for the review to finish.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Sign the plugin after it&amp;rsquo;s approved.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&#34;check-these-requirements-before-you-submit&#34;&gt;Check these requirements before you submit&lt;/h2&gt;
&lt;p&gt;To be published in the Grafana plugin catalog, your plugin must meet certain criteria. For example, it has to use one of the accepted licenses: AGPL-3.0, Apache-2.0, BSD, GPL-3.0, LGPL-3.0, or MIT. Refer to the &lt;a href=&#34;/legal/plugins/&#34;&gt;Grafana plugins policy&lt;/a&gt; for the full criteria.&lt;/p&gt;
&lt;p&gt;Grafana Labs can also decline plugins that fork or duplicate an existing plugin, bundle several plugins into one, or only work in a specific environment.&lt;/p&gt;
]]></content><description>&lt;h1 id="the-publishing-workflow">The publishing workflow&lt;/h1>
&lt;p>Follow this order to submit your plugin:&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Package the plugin, but don&amp;rsquo;t sign it yet.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Optionally, add a ready-to-run test setup for reviewers.&lt;/p></description></item><item><title>What the review process looks like</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/03-review-process/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/03-review-process/</guid><content><![CDATA[&lt;h1 id=&#34;what-the-review-process-looks-like&#34;&gt;What the review process looks like&lt;/h1&gt;
&lt;p&gt;The Grafana Plugins team runs an automated validation against its guidelines first. Your submission then sits in a queue. After that, one of the Grafana reviewers reads the code and installs the plugin to test it.&lt;/p&gt;
&lt;p&gt;Each submission is reviewed individually, so review times vary.&lt;/p&gt;
&lt;h2 id=&#34;make-the-install-and-test-step-easy&#34;&gt;Make the install-and-test step easy&lt;/h2&gt;
&lt;p&gt;Reviewers want a sample dashboard, a setup they can bring up with Docker Compose, and, for more complex plugins, a test API. Providing them can speed up your review.&lt;/p&gt;
&lt;p&gt;Refer to &lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/provide-test-environment&#34;&gt;Help us test your plugin&lt;/a&gt; for useful tips.&lt;/p&gt;
]]></content><description>&lt;h1 id="what-the-review-process-looks-like">What the review process looks like&lt;/h1>
&lt;p>The Grafana Plugins team runs an automated validation against its guidelines first. Your submission then sits in a queue. After that, one of the Grafana reviewers reads the code and installs the plugin to test it.&lt;/p></description></item><item><title>Signature levels</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/04-signature-levels/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/04-signature-levels/</guid><content><![CDATA[&lt;h1 id=&#34;signature-levels&#34;&gt;Signature levels&lt;/h1&gt;
&lt;p&gt;Every plugin is signed under a &lt;strong&gt;signature level&lt;/strong&gt;, which determines how the plugin can be distributed. How you get that level depends on whether your plugin is public or private.&lt;/p&gt;
&lt;h2 id=&#34;public-plugins-are-reviewed-first&#34;&gt;Public plugins are reviewed first&lt;/h2&gt;
&lt;p&gt;Grafana reviews public plugins before you can sign them. If your plugin is approved, Grafana assigns it one of these levels:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Community&lt;/strong&gt;: Community plugins have dependent technologies that are open source and not for profit. They&amp;rsquo;re published in the Grafana plugin catalog, and you can sign them free of charge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commercial&lt;/strong&gt;: 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&amp;rsquo;re published in the Grafana plugin catalog, and signing them requires a Commercial Plugin Subscription.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Plugins sold through the Grafana Marketplace have their own &lt;strong&gt;Marketplace&lt;/strong&gt; level. You learn about it in the next section.&lt;/p&gt;
&lt;h2 id=&#34;private-plugins-arent-reviewed&#34;&gt;Private plugins aren&amp;rsquo;t reviewed&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Private&lt;/strong&gt; plugins are for use on your own Grafana instances. They can&amp;rsquo;t be distributed to the Grafana community or to your customers, and they aren&amp;rsquo;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.&lt;/p&gt;
&lt;p&gt;Private plugins aren&amp;rsquo;t compatible with Grafana Cloud.&lt;/p&gt;
&lt;p&gt;Refer to &lt;a href=&#34;/docs/grafana/latest/administration/plugin-management/plugin-sign/&#34;&gt;Plugin signatures&lt;/a&gt; and the &lt;a href=&#34;/legal/plugins/&#34;&gt;Grafana plugins policy&lt;/a&gt; for more details.&lt;/p&gt;
]]></content><description>&lt;h1 id="signature-levels">Signature levels&lt;/h1>
&lt;p>Every plugin is signed under a &lt;strong>signature level&lt;/strong>, which determines how the plugin can be distributed. How you get that level depends on whether your plugin is public or private.&lt;/p></description></item><item><title>After you publish</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/05-after-you-publish/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/05-after-you-publish/</guid><content><![CDATA[&lt;h1 id=&#34;after-you-publish&#34;&gt;After you publish&lt;/h1&gt;
&lt;p&gt;Publishing is the start of your plugin&amp;rsquo;s life in the Grafana plugin catalog, not the end.&lt;/p&gt;
&lt;h2 id=&#34;release-updates&#34;&gt;Release updates&lt;/h2&gt;
&lt;p&gt;To release a new version, go to &lt;strong&gt;Org Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;My Plugins&lt;/strong&gt; and click &lt;strong&gt;Submit Update&lt;/strong&gt; for your plugin. Updates go through the same review as new plugins, but they&amp;rsquo;re often faster because reviewers may already have a test environment for your plugin.&lt;/p&gt;
&lt;h2 id=&#34;keep-your-plugin-current&#34;&gt;Keep your plugin current&lt;/h2&gt;
&lt;p&gt;Run &lt;code&gt;npx @grafana/create-plugin@latest update&lt;/code&gt; in your plugin folder to update its build configuration, dependencies, and scripts. This helps your plugin keep working with the latest Grafana versions.&lt;/p&gt;
&lt;h2 id=&#34;retire-your-plugin&#34;&gt;Retire your plugin&lt;/h2&gt;
&lt;p&gt;If you can no longer maintain your plugin, you can request that it be deprecated and removed from the Grafana plugin catalog. Grafana Labs may also deprecate plugins that no longer meet its standards for security, quality, and compatibility.&lt;/p&gt;
&lt;p&gt;Refer to &lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/publish-a-plugin&#34;&gt;Publish or update a plugin&lt;/a&gt; for details.&lt;/p&gt;
]]></content><description>&lt;h1 id="after-you-publish">After you publish&lt;/h1>
&lt;p>Publishing is the start of your plugin&amp;rsquo;s life in the Grafana plugin catalog, not the end.&lt;/p>
&lt;h2 id="release-updates">Release updates&lt;/h2>
&lt;p>To release a new version, go to &lt;strong>Org Settings&lt;/strong> &amp;gt; &lt;strong>My Plugins&lt;/strong> and click &lt;strong>Submit Update&lt;/strong> for your plugin. Updates go through the same review as new plugins, but they&amp;rsquo;re often faster because reviewers may already have a test environment for your plugin.&lt;/p></description></item><item><title>Resources</title><link>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/06-resources/</link><pubDate>Wed, 11 Nov 2026 06:29:02 +0100</pubDate><guid>https://grafana.com/docs/learning-hub/plugin-development/03-publish-to-the-catalog/06-resources/</guid><content><![CDATA[&lt;h1 id=&#34;resources&#34;&gt;Resources&lt;/h1&gt;
&lt;p&gt;These pages live in the Plugin Tools documentation portal.&lt;/p&gt;
&lt;h2 id=&#34;documentation&#34;&gt;Documentation&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;/legal/plugins/&#34;&gt;Grafana plugins policy&lt;/a&gt;: Signature levels, publishing criteria, and accepted licenses.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/publishing-best-practices&#34;&gt;Publishing best practices&lt;/a&gt;: Metadata, README, changelog, end-to-end tests, the validator, and GitHub Actions.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/package-a-plugin&#34;&gt;Package a plugin&lt;/a&gt;: The packaging step.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/sign-a-plugin&#34;&gt;Sign a plugin&lt;/a&gt;: Signing after approval and the different signature levels.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/publish-a-plugin&#34;&gt;Publish or update a plugin&lt;/a&gt;: Submission and the stages of review.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/provide-test-environment&#34;&gt;Help us test your plugin&lt;/a&gt;: What reviewers want to install.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;/developers/plugin-tools/publish-a-plugin/publish-faqs&#34;&gt;Publishing FAQs&lt;/a&gt;: The questions the other pages leave open.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;community&#34;&gt;Community&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://community.grafana.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Grafana Community Forums&lt;/a&gt;: Share ideas, ask questions.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://slack.grafana.com/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Grafana Slack&lt;/a&gt;: Join the conversation.&lt;/li&gt;
&lt;/ul&gt;
]]></content><description>&lt;h1 id="resources">Resources&lt;/h1>
&lt;p>These pages live in the Plugin Tools documentation portal.&lt;/p>
&lt;h2 id="documentation">Documentation&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="/legal/plugins/">Grafana plugins policy&lt;/a>: Signature levels, publishing criteria, and accepted licenses.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/publishing-best-practices">Publishing best practices&lt;/a>: Metadata, README, changelog, end-to-end tests, the validator, and GitHub Actions.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/package-a-plugin">Package a plugin&lt;/a>: The packaging step.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/sign-a-plugin">Sign a plugin&lt;/a>: Signing after approval and the different signature levels.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/publish-a-plugin">Publish or update a plugin&lt;/a>: Submission and the stages of review.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/provide-test-environment">Help us test your plugin&lt;/a>: What reviewers want to install.&lt;/li>
&lt;li>&lt;a href="/developers/plugin-tools/publish-a-plugin/publish-faqs">Publishing FAQs&lt;/a>: The questions the other pages leave open.&lt;/li>
&lt;/ul>
&lt;h2 id="community">Community&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://community.grafana.com/" target="_blank" rel="noopener noreferrer">Grafana Community Forums&lt;/a>: Share ideas, ask questions.&lt;/li>
&lt;li>&lt;a href="https://slack.grafana.com/" target="_blank" rel="noopener noreferrer">Grafana Slack&lt;/a>: Join the conversation.&lt;/li>
&lt;/ul></description></item></channel></rss>