Grafana OSS Self-Hosted

Self-hosted dashboards, visualization and alerting for operational data.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Grafana maintained-branch security patches

The 13.3.1 release and coordinated branch patches address multiple authorization, impersonation, path and availability issues.

Scope: Grafana 13.3.1; use the vendor advisory for the exact fix on maintained 13.2, 13.1, 13.0 or 12.4 lines.

Plugin and deployment configuration matter. This review does not assign one affected-version range to all CVEs.

Action: Apply the applicable branch patch and validate plugin compatibility against the individual advisories.

Primary source · Vendor advisory index · Reviewed 2026-11-17

What lands where

  1. Supplied by

    Vendor or project

    Official Linux packages, Docker image or Kubernetes Helm deployment.

  2. Operated by

    Your team

    Customer maintains the Grafana server, database, plugins, access controls and data-source integrations.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Linux packages, Docker image or Kubernetes Helm deployment.
InfrastructureServers / containers
The documented self-hosted runtime uses an application server or container with persistent state services. Hosted vendor editions are outside this listing.
Licensing modelOpen Source / Open Core
This entry specifically covers AGPL-licensed Grafana OSS. Grafana Enterprise and separately licensed enterprise plugins are outside that OSS scope.
LicenseAGPL-3.0 OSS; Enterprise distribution/plugins have separate licensing

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

Grafana OSS supports Generic OAuth, including compatible OIDC providers, and named OAuth integrations. Configure trusted identity claims, account linking and organization roles. SAML and some synchronization/policy features remain Enterprise/Cloud-only; their paid scope does not make all OSS SSO edition-dependent.

Grafana OSS user login; clarifies free OAuth versus paid SAML/advanced synchronization · Source ↗ · Authentication method and feature comparison ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official Docker guide runs the Grafana OSS image with persistent data and configuration; packages and Helm are separate paths. Pin the released OSS image, configure the database, credentials, plugins, TLS/reverse proxy and backups. The Grafana application does not deploy its metrics, logs or traces backends for you.

Official OSS application installation, not the separately licensed Enterprise image or a complete observability stack · Source ↗ · Deployment artifact ↗ (select the OSS image tag matching the reviewed application release; v13.3.1 release snapshot) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The install guide treats 1 core/512 MB as an evaluation floor. Its small application tier starts at 2 cores and 2–4 GB RAM; medium examples use larger, load-balanced instances and an external database. Metrics/log/trace stores and rendering capacity are separate, so these figures do not size 1 TB of telemetry or the full HA observability stack.

Grafana server sizing tiers only; database and observability backends require separate capacity · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The published Grafana v13.3.1 OSS application uses AGPLv3. Grafana Enterprise/Cloud features, commercial plugins and support have separate terms; an Enterprise download or marketplace offer does not change the OSS licence or include a commercial entitlement. Budget data backends and infrastructure separately.

Grafana OSS application software terms, distinct from Enterprise/Cloud services · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The publisher-designated GitHub release checked was v13.3.1, published 2026-11-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.

Upstream grafana/grafana release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers Grafana OSS, not Grafana Cloud. The Enterprise Docker image and plugins can have different terms and entitlements. Grafana queries configured data sources; it is not by itself a complete logs/metrics storage backend. Grafana 13.3.1 fixes multiple authorization, impersonation, path-traversal, and denial-of-service CVEs; coordinated patches were also published for maintained 13.2, 13.1, 13.0, and 12.4 branches. Upgrade to a patched release for the deployed branch and review plugin compatibility.

Category fit

Observability
Visualization, dashboards and alerting over connected telemetry and other data sources; storage backends are configured separately.

Compare within Observability

  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    Customer-operated · Open Source / Open Core
  • Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · vendor control plane · Commercial Only
  • Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
    • AWS
    • Azure
    • Google Cloud
    • Railway
    • Render
    Customer-operated · Open Source / Open Core
  • MLflow Tracking Server Self-HostedSelf-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Self-managed Grafana OSS in an EKS monitoring stack ↗ · AWS

      Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      AWS documents kube-prometheus-stack pods in a customer EKS cluster, including the Prometheus Server StatefulSet and Grafana application. This evidence covers those self-managed components, not Amazon Managed Grafana or Amazon Managed Service for Prometheus. Review persistence, retention, authentication and cluster operating costs.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory