Every platform team hits the same wall at the same time. Prometheus is excellent at scraping a cluster and terrible at remembering anything: retention is bounded by the node's disk, the query path lives or dies with one server, and "give us per-team cost and isolation for two hundred clusters" is simply not a question Prometheus was built to answer. The Prometheus design position on this has not moved in a decade — local disk, no clustering, remote write for everything else.

That refusal is why the remote-write ecosystem exists at all, and the two big answers are Thanos and Grafana Mimir. We already covered the VictoriaMetrics alternative in VictoriaMetrics vs Prometheus and the storage-end of the Prometheus 3.x line in Prometheus 3.15.0 release notes. This guide is about Mimir — and specifically about the reason you actually run it: not retention (S3 gives you that), but multi-tenancy with per-tenant cardinality guardrails, enforced in one place, hot-reloaded at runtime.

What we did: ran the real thing. Grafana Mimir 3.2.1 (sha256-verified release binary, go1.26.7) on a single host, plus Prometheus 3.15.0 remote-writing into it as two different tenants. We pushed a 6,000-series burst into a tenant capped at 5,000 series, watched the cap hold exactly, watched the remote-write client drop the excess on the floor, then fixed tenant limits live via hot-reload without touching the server. Every error message, metric value, and config key below is real output from that run — not documentation paraphrase.

1. The Structural Shift: From Local Disk to a Multi-Tenant Facts Store

Prometheus's model is a cache: scrape, keep in TSDB head, compact to local blocks, expire. The ecosystem's remote-write receivers are the system of record. Once metrics leave the cluster, three things you could never get from Prometheus itself become possible — and they are the entire justification for a Mimir deployment:

  • Tenancy. One X-Scope-OrgID header separates every write and read. Two Prometheus servers writing to the same Mimir never see each other's series. We verified this live: tenant-a answered up == 1; the same query under tenant-b returned zero series.
  • Per-tenant limits as a first-class API. Series caps, ingestion rate, query length, fetched-series-per-query — all set per tenant in a YAML file that reloads every 10 seconds. The noisy-neighbor problem gets a blast radius instead of a pager.
  • Cardinality as an observable, budgeted resource. Mimir counts active series per tenant and per custom matcher class, so "who blew up the metrics bill" is a query, not an archaeology dig.

The honest framing: Mimir is the Cortex lineage productized. Grafana forked Mimir from Cortex in March 2022 to pay down accumulated technical debt, kept the battle-tested distributor/ingester/store-gateway split, and made object storage the only source of truth — we traced the history in the Prometheus oss-tale. It scales absurdly (Grafana's own 1-billion-active-series load test, single tenant), it is AGPL-3.0, and it is the engine behind Grafana Cloud's managed metrics. The commercial path exists in two shapes if you don't want to run it: Grafana Cloud (SaaS) and Grafana Enterprise Metrics (self-managed, paid features) — the open source chart deploys either.

Who should skip this guide: if you have one cluster and one team, Mimir is a distributed-systems tax you don't owe. Keep Prometheus local, or use its retention features, and revisit when per-team isolation becomes a real requirement.

2. Architectural Blueprint

Mimir's components map to a single data plane: writes fan out through distributors to a ring of ingesters (in-memory TSDB heads), blocks ship to object storage, and reads go through a query-frontend that splits and caches. The write path and read path have different URL prefixes — a live trap we hit in testing (writes are /api/v1/push, reads are /prometheus/api/v1/...):

   Prometheus (cluster A)          Prometheus (cluster B)
        | remote_write                     | remote_write
        | + header X-Scope-OrgID: team-a  | + header X-Scope-OrgID: team-b
        v                                 v
   +------------- HTTP: /api/v1/push -------------+
   |                  DISTRIBUTOR                  |
   |  per-tenant rate limit (429, retryable)       |
   |  replication by consistent-hash ring          |
   +----------------------+------------------------+
                          v
                  +------- INGESTERS -------+   in-memory TSDB head
                  | ring: N x RF replicas   |   per-tenant series cap
                  | (memberlist KV store)   |   (400, NON-retryable)
                  +-----------+------------+
                              | 2h blocks
                              v
                  [ OBJECT STORAGE  S3 / GCS / Azure ]
                              ^
                              | compaction + retention
                  +-----------+------------+   +----------------+
                  |       COMPACTOR         |   |    RULER       |
                  +--------------------------+   | (rule eval,    |
                                                 |  alerting)     |
   +------------- HTTP: /prometheus/api/v1/ ----+----------------+
   |                QUERY-FRONTEND                 |  split + cache
   |  per-tenant query limits, sharding (3.2: on)  |
   +----------------------+------------------------+
                          v
                     QUERIERS  ----- store-gateways (bucket index)
                          |
                          v
                    Grafana / your tools