Kris Lahiri: There is another angle which is what you were referring to. I’ll bring up Egnyte in the life sciences space. Nowadays, there’s a lot of very serious work being done by life sciences companies that are using either genomics or other types of DNA sequencing, which needs a huge amount of elastic compute.
It’s a perfect environment for what happens in the public cloud like Google Cloud and AWS. The results of those experiments is what they need to collaborate on.
The whole drug development world is morphed into lots of third-party collaborators. There are people referred to as clinical research organizations. There may be some doctors that they’re working with at MIT or something like that.
This collaboration with third-party companies still needs to be performed on a platform that they trust. That’s where Egnyte is adjacent to what is happening in the public space. Genomics and all that DNA sequencing is happening in AWS, but a subset of those results are used by an Egnyte integration with an AWS or some of these public cloud environments to collaborate on.
Sramana Mitra: AWS is a horizontal public cloud platform. What about areas where there’s a lot of domain knowledge and domain-based workflow, and algorithms built in?
In the CRO space, take Medidata. Medidata is heavily involved in heavy-duty capabilities and algorithms within the clinical research space. How does Egnyte interface with a Medidata?
Kris Lahiri: That’s a very good question and that’s at the core of our whole ecosystem and platform strategy. Think of Egnyte as the core workflow for the place where the end data resides. It’s the pipes that let you collaborate securely with people.
The actual work that someone is doing is happening at these end points. We’ll stick to the life sciences workflow for just a second, and then I’ll give you some other examples as well. On the life sciences side, Egnyte integrates through our API strategy with an RSpace where someone who’s running experiments are really looking at that flow.
They don’t really have to worry about, “I now need to switch out and use some other solution.” They continue to work on their core platform for that job. Egnyte is the background plumbing that will help them integrate or interact with other people.
That is all done through some type of centralized, easy, managed way in which IT is involved. A doctor or a scientist doesn’t have to worry about the rules of engagement in terms of third parties.
Another angle where we’ve seen the whole ecosystem has evolved is in construction or AAC world. We’ve got so many examples. Let’s say someone is doing a complicated building. They will have many subcontractors come in in many phases. There’s some very interesting integrations that Egnyte has built with other systems of choice.
Take for example, Procor where the actual design doc is being done by the engineers on site in their platform. In the background, that data resides in Egnyte. That happens through our integration with Procor. The rules of who can see it and the sharing capabilities is handled by Egnyte.