[bottlewhistler]

This is very interesting! Super cool features, I'm sure many non-technical stakeholders will find value in this solution.

On the security aspect: users will need to trust that you are only querying the schemas, and that you are not accessing the data in the databases? My understanding is that (regardless of the SQL flavor) you cannot grant access to read only the names of the schemas/tables without granting access to the data they contain.

Do you envision larger (corporate) customers not being able to subscribe to your service because of these security concerns? Do you think there is any way in which you can bypass this limitation, e.g. by installing an on-premise client which holds the access credentials and never shares them with your servers?

[jleguina]

This is a great point. Indeed, we aim to facilitate on-prem deployment as much as possible, as that guarantees security and data privacy.

We want to get as many users on board as we can to hear what their thoughts are and build in that direction - on-prem definitely ranks high!