Seeking Grafana guidance on whether a Community App Plugin can safely rely on the public EmbeddedDashboard API while it remains marked @alpha.

Grafana Plugin Development
1

I’m developing a Grafana Community App Plugin intended for eventual submission to the Grafana Plugin Catalog.

The app needs to render an existing Grafana dashboard by UID inside the plugin without requiring users to manually reconstruct their dashboards. The public EmbeddedDashboard export from @grafana/runtime provides the capability I need, and I have validated it with Grafana 13.2.

However, the TypeScript declaration currently marks EmbeddedDashboard as @alpha.

For a Grafana Community App Plugin, is it considered acceptable for the core workflow to depend on the public @grafana/runtime EmbeddedDashboard export while it is marked @alpha, or would Grafana recommend avoiding that dependency for a plugin intended for Catalog publication?

I’m primarily trying to understand the expected plugin-development/publication boundary before building more of the product around this API.

2

It may remain in alpha for ages. Set the supported Grafana version boundaries in plugin.json. If they drop it from the /runtime later, you’ll adapt.

It is normal to have ‘private/public preview’, ‘alpha’ badges on plugins/features kept for years, without promotion to stable. Grafana labs constantly fires and drops something - not that there’s a clear 100% policy