[disgruntledphd2]

> This is solving a problem few people have. They assume your table name, column names and relationships is confidential information. For most people such metadata is not confidential.

For most businesses, it really really is. In general, people (businesses) are incredibly sensitive about any possibility of data leakage, even just the metadata. There are lots of companies who would pay for this, and they tend to have a lot of money.

[munk-a]

This would be a (small, granted) red flag for me about a company. As a data architect I work really hard to make sure our model is legible and obvious - the way which the model is adopted to our problem area is certainly a difficult problem that is valuable to have solved. But minor details of that schema should be extremely boring.

[disgruntledphd2]

Like, I've never really been sure why people care about this so much. However, when I worked for a data observability company where we took in and did work on a lot of this metadata, it became apparent that lots of our customers cared.