Polyer

Grafana

Deploy Grafana on Polyer to build dashboards and alerts from metrics, logs and databases. This template runs one grafana/grafana-oss service on a public domain, keeps its data and default SQLite database on a volume at /var/lib/grafana and generates the admin password. Review the untagged image, which tracks the latest release.

MonitoringCoolify open catalog

What you can use it for

  • Build dashboards for metrics from Prometheus, SQL databases and other data sources you already run.
  • Define alert rules on application metrics and send notifications to your team.

What this template creates

grafanagrafana/grafana-oss
Public endpoint Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Sign in as admin with the generated password stored in SERVICE_PASSWORD_GRAFANA. Grafana applies GF_SECURITY_ADMIN_PASSWORD only when it first creates the admin user, so change the password inside Grafana afterwards rather than in the variable.
  • Dashboards, users, plugins and the SQLite database live in /var/lib/grafana on the volume; check backup and recovery and test a restore before relying on it. GF_SERVER_ROOT_URL and GF_SERVER_DOMAIN are set from the generated domain, so update them if you serve Grafana from another address.
  • The grafana/grafana-oss image has no version tag, so a redeploy can bring a newer major release; consider pinning a version and read the upgrade notes first. Grafana does not collect data itself: Prometheus, Loki or databases you connect are separate services with their own costs.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Choose your next step