Should I self-host Grafana Cloud?

YESworth it

Grafana OSS is the same dashboards without the per-seat cloud math — the honest catch is that Cloud's bundled Prometheus/Loki storage becomes your problem.

The math (nothing hidden, including your time)

Grafana Cloud (Pro)	$19.00/mo
VPS share + storage	−$1.50/mo
Your maintenance: 20 min/mo at $20/h	−$6.67/mo
Net saving	$10.83/mo
Setup: 45 min measured (one-time)	$15.00
Break-even	1.4 months
Markup Index (price ÷ real self-host cost)	2.3×

What's your hour worth? $20/h$0/h = "my homelab time is free and I love it" — a legitimate position

Price: source, checked 2026-08-06. Inputs are stored in git; every number above is derived, never hand-written.

What you lose

Managed Prometheus/Loki/Tempo storage — you now run (and size) your own data sources
Cloud's SLO on the thing that pages you

What you're paying Grafana Cloud for

dashboards over your metrics/logs
alerting
team sharing
plugin ecosystem

Grafana OSS running from the boot-verified compose file — Grafana OSS, running from the compose file on this page — screenshot from our verified instance, not marketing material.

Ranked alternatives

1. Grafana OSS

Dashboards and alert rules over data you already have, from one container, with no active-series quota and no per-user bill.

grafana/grafana · ★ 76,206 · last commit 0d ago · AGPL-3.0

Hardware

Runs comfortably on Raspberry Pi.

The tested compose file (our evidence, CI-booted)

# Grafana OSS — same dashboards, no per-seat cloud bill (replaces Grafana Cloud Pro for
# small teams; you bring your own Prometheus/Loki, which is the honest catch)
services:
  grafana:
    image: grafana/grafana:latest
    container_name: grafana
    restart: unless-stopped
    ports:
      - "3002:3000"
    volumes:
      - grafana-data:/var/lib/grafana
    healthcheck:
      test: ["CMD-SHELL", "curl -sf http://localhost:3000/api/health || exit 1"]
      interval: 5s
      timeout: 5s
      retries: 24
      start_period: 20s

volumes:
  grafana-data:

Want a guided install instead? caniselfhostit.com/grafana-cloud has AI-agent prompts that assume a bare machine — that's their half of the stool, and it's good.

Verification

Protocol v1 · verified by zernonia on 2026-08-10 · setup measured at 45 min · AI assistant: claude-code (allowed & stated)

What broke

Nothing for Grafana itself — the real setup time is in the data sources it points at

Full timed log

# Timed setup log: Grafana Cloud → grafana

**Protocol:** v1 · **Verified by:** zernonia · **Date:** 2026-08-10
**Assistant:** claude-code · **Environment:** containerized runner, 2 vCPU class, Docker 29.3 / Compose v5.1

## Timeline

| Step | Time |
|---|---|
| Read upstream docs, draft compose with healthcheck | ~15 min |
| **Boot: all services healthy in 73 s (measured, `compose up --wait`)** | — |
| Endpoint-level workflow check (login/health/API serve) + re-run from clean volumes | ~15 min |
| **Total: ~45 min** | |

Boot and endpoint checks are machine-verified; `setup_min` is the wall-clock total for this
session including authoring, diagnosis and re-runs. Endpoint-level ≠ full human UI workflow —
dispute anything that doesn't reproduce (CONTRIBUTING.md).

## What broke

- Nothing for Grafana itself — the real setup time is in the data sources it points at

## Verdict-relevant notes

- Verdict scope: replacing Grafana Cloud Pro for a small stack that already has (or can run) its own Prometheus. If you want managed everything, that's the product you're paying for.

Verdict history

2026-08-10: unscored → YES — Initial verdict: Grafana OSS is the same dashboards without the per-seat cloud math.