[Ajs1]

Co-founder here. Understand your concern and perspective Brad. In the near term this is a SaaS offering, so the best we can do to address these concerns is to offer strong security controls (a short list on our site, longer list on request) backed up by external certification (underway). Plus the credibility and track records of the team behind it.

[eps]

I’m going to echo the GP - this does look like an interesting tech, but it must work in a privacy-preserving fashion. Logs contain loads of sensitive info, especially if they are of a verbose/debug type, which is what will probably be used to capture failures. But in SaaS form, where it wants raw logs, it’s a no-go even for the eval purposes.

[gdcohen]

Gavin from Zebrium here. Again, we understand this concern. All data is encrypted in-flight and at rest and we have a lot of security controls in place (see our website). We also have the option of a dedicated VPC assigned to a single customer. Beyond this, we have a unique capability: since our machine learning structures and types everything, we have a feature that lets us hash (or delete) any sensitive information in logs (and we can record match to find other places this info occurs that you might not even be aware of). Not dodging the fact that we're SaaS, just pointing out what we do.