Maintainers

Subsystem ownership at Grafana is encoded in .github/CODEOWNERS (1,384 lines). The file is the single source of truth — this page summarizes the squads mentioned there and which directories they cover.

Squad ownership tends to be stable across releases. Individual contributors come and go; the easiest way to get in touch with a squad is via Grafana Community Slack (#grafana-<squad> channels) or a GitHub @grafana/<squad-name> mention.

Squads and their domains

Squad	Owns (representative paths)
@grafana/grafana-backend-services-squad	/.changelog-archive, /CHANGELOG.md, pkg/services/featuremgmt, parts of pkg/services/, server release tooling
@grafana/grafana-frontend-platform	public/app/core/, public/app/features/dashboard*, frontend infra
@grafana/grafana-app-platform-squad	apps/, pkg/storage/unified/, pkg/services/apiserver/, pkg/aggregator/
@grafana/dataviz-squad	Built-in panel plugins, public/app/features/visualization/, @grafana/ui
@grafana/dashboards-squad	public/app/features/dashboard-scene/, public/app/features/dashboard/, apps/dashboard/
@grafana/explore-squad	public/app/features/explore/, related backend
@grafana/alerting-frontend / @grafana/alerting-backend	public/app/features/alerting/, pkg/services/ngalert/, apps/alerting/
@grafana/identity-access-team	pkg/services/auth*, pkg/services/accesscontrol, pkg/services/ldap, apps/iam, SSO-related code
@grafana/data-sources-plugins	pkg/tsdb/*, public/app/plugins/datasource/*, plugin SDK integrations
@grafana/plugins-platform-frontend / @grafana/plugins-platform-backend	pkg/plugins/, pkg/services/pluginsintegration/, public/app/features/plugins/
@grafana/grafana-search-and-storage	pkg/services/store/, pkg/services/search/, pkg/storage/unified/search/, related infra
@grafana/o11y-traces-and-profiling	Tempo, Jaeger, Zipkin, Pyroscope, Parca code (frontend + backend)
@grafana/observability-logs	Loki + logs-related UX
@grafana/observability-metrics	Prometheus + metrics-related UX, drilldown
@grafana/aws-datasources	CloudWatch and adjacent AWS integrations
@grafana/azure-grafana	Azure Monitor and adjacent integrations
@grafana/partner-datasources	Cloud Monitoring (GCP) and other partner-maintained sources
@grafana/scim-team	SCIM provisioning
@grafana/grafana-operator-experience-squad	Grafana operator(s), CI tooling for app-platform
@grafana/cloud-migration-squad	pkg/services/cloudmigration/, public/app/features/migrate-to-cloud/
@grafana/grafana-as-code	Provisioning & GitOps experiences (apps/provisioning/)
@grafana/docs-grafana / @grafana/docs-tooling	docs/, README.md, .vale.ini, this wiki's source dirs
@grafana/grafana-community-support	CONTRIBUTING.md, CODE_OF_CONDUCT.md, community-facing docs

How to find owners for a specific path

# Quick lookup
grep -n '<your/path>' .github/CODEOWNERS

The last matching pattern in CODEOWNERS wins, so check the bottom of the file for fine-grained overrides before assuming the broad pattern applies.

Per-directory AGENTS.md

Some squads keep additional onboarding docs co-located with their code:

• AGENTS.md — repo-wide AI agent guide (also useful for humans).
• docs/AGENTS.md — documentation style guide.
• public/app/features/alerting/unified/AGENTS.md — alerting frontend patterns.

When you start work in an unfamiliar directory, look for an AGENTS.md first.

See also

• .github/CODEOWNERS — the canonical owner mapping.
• How to contribute / index — contributing process.