Sorry, our demo is not currently available on mobile devices.

Please check out the desktop version.
You can learn more about Stemma on our blog.
See Our Blog
close icon
November 9, 2022
March 9, 2022
-
min read

Stemma vs. Amundsen

by
Mark Grover
Co-founder, CEO of Stemma
Share This Article

NOTE: For the most current comparison between Stemma and Amundsen, read How Stemma Upgrades Amundsen

Stemma is inspired by Amundsen, the automated data catalog created at Lyft that’s used by Instacart, Brex, ING, Square, and many more.

Stemma focusses on three main areas of investment, on top of Amundsen:

1. Secure & managed offering with easy administration

Stemma provides:

  • A managed deployment, with SSO integration, security, auditing, backup/restore and much more
  • Ability to simply plug in credentials to ingest data - no need to run Python databuilder jobs to ingest metadata
  • Admin panel that enables you easily administer your stemma deploy - how many users are using the product, what most used tables are missing documentation, etc.
Stemma Admin panel showing number of tables and dashboards without documentation or ownership

2. Lower time to value through automation

This is an area of constant investment and evolution for Stemma. Some recent investments here include:

  • Automated table and column level lineage through query parsing
  • See commonly used with tables, through parsing of query logs
  • Bulk editing to apply ownership and other metadata in bulk
  • Share descriptions across related columns
  • Link related Slack conversations via a Slack bot
  • Suggestions on what data to use
Apply ownership and other metadata in bulk via Stemma

3. Focus on adoption and building decentralized, data-informed culture

Stemma team works with you to ensure adoption and success of your data catalog as we have done with dozens of companies. See more details here.

Share This Article
Oops! Something went wrong while submitting the form.

Next Articles

November 9, 2022
June 21, 2022
-
4
min read

Balancing Proactive and Reactive Approaches to Data Management - Part 1

Data management is best handled by balancing proactive and reactive methods

November 9, 2022
October 7, 2021
-
min read

3 Steps for a Successful Data Migration

Learn the 3 crucial steps that great data engineering teams follow for a successful data migration.

November 9, 2022
October 4, 2021
-
min read

Making Sense of Metadata Ingestion

One of the early questions that data engineering teams pose when implementing a catalog is: should we make the catalog responsible for gathering metadata from data systems ("pull"), or task data systems with reporting metadata to the catalog ("push")? And, what are the consequences of using one approach over the other? Learn how to ingest metadata into your catalog and which method to choose.