3 ms·

So is the value-add that the customers of Company-A (who is your customer) entrust you with credentials to their databases versus entrusting Company-A with them

• ctc24 4y ago
  That can be part of the value-add, though for on-prem deployments, we never touch the credentials ourselves. Not to sound like a consultant, but there's three value-adds I'd call out: 1. Handling the dialect, types, and connection modalities of many different databases. This takes a lot of time to build and there's a lot of nuance that's non-trivial to work through. 2. Replicating data and guaranteeing data integrity + reliability. There's again a lot of nuance here, especially once you start considering that data is eventually consistent in most sources, that you want to transfer it as efficiently as possible, etc. 3. Providing a clean UX that end-customers can use out of the box, such that the end-customer experience is clean and intuitive. We spend a lot of time thinking about how it makes sense for people to connect their data, so that our customers don't have to. edit: fmt