Support for Custom Domains

Hi team, We'd love the ability to give our Grafana instance a friendly alias on a custom domain (e.g. `grafana.example.com`). Would this be something on the roadmap? Cheers

GitHubToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

medium confidence

Competition

No competitor data yet

Trend

No signal yet

Custom domain support for Grafana, a quality-of-life feature addressing branding and accessibility needs for enterprise monitoring deployments.

The pain

Teams running Grafana instances must use default URLs (IP addresses or auto-generated domains), creating friction for: (1) internal branding/professionalism, (2) sharing dashboards with stakeholders, (3) DNS-based access control, (4) SSO/authentication integrations that require consistent domains.

The gap

Grafana likely supports this via reverse proxy configuration, but users are requesting native, first-class support, suggesting the current workaround is non-obvious, poorly documented, or requires DevOps expertise that product teams lack.

Build angle

This is a feature request, not a business idea. However, if positioned as a service: (1) Managed Grafana hosting with custom domains as a differentiator, (2) A lightweight reverse proxy/DNS management tool for Grafana deployments, or (3) A Grafana plugin/extension simplifying domain configuration.

Strengths

  • Clear, specific user need from active Grafana community
  • Low technical complexity, standard reverse proxy/DNS problem
  • High perceived value for enterprise/mid-market users
  • Addresses both UX and security concerns
  • Likely quick to implement if building as plugin or managed service

Risks

  • Grafana may already support this; request may reflect documentation/UX gap rather than missing capability
  • Feature request ≠ business opportunity; limited TAM if only solving for Grafana users
  • Reverse proxy solutions (Nginx, Caddy, Cloudflare) already solve this generically
  • If building as plugin: Grafana's roadmap may include this natively, making it obsolete
  • Low switching costs; users can migrate to competitors if they add this feature first
  • Unclear if this is a bottleneck to adoption or a nice-to-have

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Support for Custom Domains”.

Open FlyBot