Grafana Stack
Dashboards, metrics, and logs for your whole project - Grafana, Prometheus, and Loki pre-wired, for $13/month flat.
One-click deploy, from $13/mo on a Miget plan.
Observability SaaS has the most creative meters in the industry: per host, per million spans, per GB ingested, per active series. The open-source answer has been stable for years - Grafana for dashboards, Prometheus for metrics, Loki for logs - and it deploys beautifully as one small stack.
This template wires the three together: Grafana public with both datasources pre-provisioned, Prometheus private with a baked config (the officially documented pattern) you extend with your apps’ /metrics endpoints by service name, and Loki private in its stock single-binary filesystem mode - apps push logs straight to its HTTP API.
Deliberately absent: node-exporter and cadvisor, which need host access a PaaS cannot grant - node metrics are the platform’s job. This stack is for your applications’ metrics and logs, which is the part you actually dashboard.
Upstream project: Grafana + Prometheus + Loki
#what you get
- Grafana with Prometheus + Loki datasources provisioned out of the box
- Prometheus: 15-day retention default, scrape any in-project app by service name
- Loki: zero-config single-binary mode; push logs from any logging library
- One $13/month plan instead of per-host / per-GB / per-series meters
- Baked-config images - edit two small files to extend, redeploy to apply
- Alerting via Grafana (email, Slack, webhooks) included
#topology
| Service | Role | Public |
|---|---|---|
| grafana | dashboards (:5000) | yes |
| prometheus | metrics, baked config (:9090) | no |
| loki | logs, filesystem mode (:3100) | no |
#miget sizing
// this stack needs
1.5 GiB RAM · 22 GB disk · 3 services
Right-sized for project-scale observability: 512 MiB per component. Prometheus RAM scales with active series, Loki disk with log volume - both have a long runway in this footprint.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Grafana Stack on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| Grafana Cloud | Pro (usage) | usage-based | $19/mo base + $6.50 per 1k active metric series + ~$0.55/GB logs all-in; the free tier is genuinely generous |
| Datadog | Infrastructure Pro | ~$15 | per host per month (annual; $18 on-demand) - before logs, APM, and custom-metric add-ons |
Observability meters compound with growth; a flat self-hosted stack turns the bill into a constant.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1.5 GiB RAM, 22 GB disk, 3 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$75 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$27 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$23 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$18 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$12 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
grafana-stack -
Set the required variables:
GF_ADMIN_PASSWORD, Grafana admin loginGF_ROOT_URL, set to the app’s https domain after first deploy
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/grafana-stack
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How does this compare to Datadog or Grafana Cloud?
Datadog Infrastructure Pro is $15-18 per host per month before logs and custom metrics. Grafana Cloud has a genuinely generous free tier, but the Pro meters ($6.50 per 1k metric series, ~$0.55/GB for logs all-in) compound with growth. This stack is $13/month flat - the same Grafana, your retention rules.
How do my apps get metrics into it?
Expose /metrics with any Prometheus client library, add the service name to prometheus.yml in the template, redeploy. In-project targets are scraped over the private network - nothing public required.
How do logs get into Loki?
Apps push directly to http://loki:3100/loki/api/v1/push - every major logging library has a Loki sink, and OTLP works too. (Promtail reached end-of-life in March 2026, and on a PaaS there are no host log files to tail anyway - pushing is the right model.)
Why no node-exporter or cadvisor?
Both need host-level access (host network, /proc, the Docker socket) that platform sandboxes cannot grant - and node health is the platform’s responsibility anyway. Application metrics and logs are what this stack is for.
Ship Grafana Stack today
One compose stack, 1.5 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.