OSS data discovery and metadata platform from Lyft. Apache-2.0 under Linux Foundation. Search-driven UI for finding tables, dashboards, ML features. Older than OpenMetadata/DataHub but mature.
Amundsen is an OSS data discovery + metadata platform from Lyft — Apache-2.0 license, ASF-graduated. Search-driven UI for finding tables, dashboards, ML features. Older than OpenMetadata/DataHub but mature. Pick Amundsen for discovery-focused catalog where Lyft-style PageRank-inspired search is the value prop.
Amundsen's discovery-first design (vs full governance) is intentional: it's a data catalog optimized for 'find the right table' rather than 'control who accesses it'. From a Trust Before Intelligence lens, this is honest scope — Amundsen does discovery well; for governance + lineage + ABAC, OpenMetadata or DataHub fit better. The audit found Amundsen's GOALS=15 reflects this honest scope, not a scoring error.
ES-backed search.
Natural-language search.
Read-mostly. Cap rule applied.
Multi-cloud, K8s.
Metadata + ownership + popularity.
Cap rule applied: less detailed than peers.
1/6 -> 2.
1/6 -> 2.
3/6 -> 3.
Discovery + ownership taxonomy.
5/6 -> 4.
Best suited for
Compliance certifications
OSS Apache-2.0 only.
Use with caution for
OpenMetadata for full governance. Amundsen for discovery focus.
View analysis →DataHub for richer governance + lineage. Amundsen for discovery search ergonomics.
View analysis →Role: L3 discovery-focused metadata platform.
Upstream: Crawler-based metadata ingestion.
Downstream: Discovery UI + search.
Mitigation: Document scope. For governance, use OpenMetadata/DataHub alongside or instead.
Amundsen's specialty.
OpenMetadata fits.
This analysis is AI-generated using the INPACT and GOALS frameworks from "Trust Before Intelligence." Scores and assessments are algorithmic and may not reflect the vendor's complete capabilities. Always validate with your own evaluation.