← Back to home
Comparison · Analytics

Amundsen vs Grafana Loki

A side-by-side editorial comparison of Amundsen and Grafana Loki — release velocity, themes, recent moves, and the top alternatives to consider.

Amundsen vs Grafana Loki: at a glance

FeatureAmundsenGrafana Loki
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesdata-catalog, metadata, maintenance-mode, monorepo-releaseslogging, observability, major-release, storage
Last editorial update3mo ago12h ago
WebsiteVisit →Visit →

What is Amundsen?

Amundsen's last release was a config flag, and the feed has been silent for two years

Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.

Read the full Amundsen trajectory →

What is Grafana Loki?

Loki 4.0 reaches RC3 and narrows S3 storage classes to Standard and Standard-IA.

Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.

Read the full Grafana Loki trajectory →

Amundsen vs Grafana Loki: editorial side-by-side

A
Amundsen
ANALYTICS
0.0

Amundsen's last release was a config flag, and the feed has been silent for two years

◆ Current state

Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.

◆ Where it's heading

The direction is contraction. Python 3.7 support was dropped and the matrix narrowed to 3.8 and 3.9 before 3.10 was cautiously added to everything except the metadata service, contributor names moved to emeritus status, and organisations were removed from the README's adopter list. What feature work exists is small and peripheral — a PowerBI logo, aggregated alerts, a gremlin proxy method — rather than anything touching how the catalog works. Nothing has been published since August 2024.

◆ Prediction

There is no signal in these entries of planned work, and a two-year silence following a single-flag release means the practical expectation is no further releases; the component version skew across databuilder, metadata and frontend is now frozen where it stopped.

G
Grafana Loki
ANALYTICS
6.3

Loki 4.0 reaches RC3 and narrows S3 storage classes to Standard and Standard-IA.

◆ Current state

Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.

◆ Where it's heading

Each candidate trims a bit more legacy surface, so 4.0 is a cleanup major that pushes installs onto TSDB and the microservices or single-binary layouts. The Operator had prepared this path since 0.11 and 0.12.

◆ Prediction

Expect a few more RCs with small breaking changes, then 4.0.0 GA and an Operator release that drops the removed schemas.

Alternatives to Amundsen and Grafana Loki

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Amundsen or Grafana Loki.

See all Amundsen alternatives → · See all Grafana Loki alternatives →

Recent activity from Amundsen and Grafana Loki

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoGrafana LokiLoki 4.0 RC3 limits S3 storage classes to Standard and IA
  2. 4d agoGrafana LokiLoki 4.0 RC1 lists the breaking changes for the major
  3. 5d agoGrafana LokiLoki 4.0 RC drops legacy storage backends and SSD mode ⚡
  4. 18d agoGrafana LokiLoki Helm chart 7.5.0 released
  5. 1mo agoGrafana LokiLoki Operator 0.12 requires schemas, adds OpenShift 5.0 TLS
  6. 2mo agoGrafana LokiLoki Operator 0.11 enables multi-variant queries
  7. 2y agoAmundsenDatabuilder 7.5.1 adds implicit-transaction config for the neo4j extractor
  8. 2y agoAmundsenDatabuilder 7.5.0 is dependency bumps and a Python 3.10 matrix
  9. 2y agoAmundsenMetadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup
  10. 2y agoAmundsenFrontend 4.3.0 republishes the same changelog under a second tag
  11. 2y agoAmundsenCommon 0.32.0 republishes the same changelog under a third tag
  12. 2y agoAmundsenMetadata 3.12.3 clears frontend dependency vulnerabilities

Frequently asked questions

What is the difference between Amundsen and Grafana Loki?

They serve adjacent needs but don't currently overlap on shipped themes. Grafana Loki is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Amundsen better than Grafana Loki?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Grafana Loki is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to Amundsen?

Top Amundsen alternatives in Analytics are ranked by recent ship velocity. Browse the "Amundsen alternatives" section above for the current picks, or visit /alternatives/amundsen for the full list with editorial commentary on each.

What are the best alternatives to Grafana Loki?

Top Grafana Loki alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Loki alternatives" section above for the current picks, or visit /alternatives/loki for the full list with editorial commentary on each.