It’s certainly possible that DataDog pays Elastic but I think it’s unlikely. A lot of modern software is built on a variety of open source components stitched together with a few add ons or an application interface to create a new proprietary product.
We could spend a lot of time on DataDog/Elastic infrastructure make up. Elastic is definitely mission critical to the core function of the DataDog SaaS applications. DataDog has other important pieces to their platform namely the DataDog agent that gets installed on the endpoints to ship to the Elastic servers. That is part of their CAP. With others in the space, I feel the UI and collector agents present a smaller CAP than having the more powerful indexing and searching function proprietary to you(and under your control).
On the other hand, having competitors have access to your core would be the bear case to that CAP. I think this and that Coinbase case are good examples of both the bull and bear cases.
Elastic is the undisputed leader for indexing, searching, and logging. Coinbase starts with Elastic clusters and x-pack. Started with open source, but they need the field and document level security features and support. Data explodes (like it is for everyone but especially them all at once). Self managing is becoming a bear and since they don’t really have the resources and know how to deploy it correctly, performance suffers. They purchase DataDog to gain visibility into Elastic, ironically using Elastic to log and monitor Elastic with a different viewing glass.
Discovering their problems and limitations they make the wise choice to host the solution. This was about a year or more ago. Elastic’s own hosted service was much smaller and less differentiated than it is today. It’s actually quite amazing how it has changed in just a year. They go with AWS Elasticsearch Service, getting the most basic version of Elastic. They mention they liked that it was in Amazon market place and AWS unified billing, both of which Elastic now has. Solves some of their problems and opens up others. Namely they don’t have the proprietary field and document level security features. They work around that by creating more clusters where they can control access by managing the higher level access to the cluster(doesn’t seem very practical and the only other option Search Guard is effectively off the table now).
This type of thing is occurring at thousands of organizations every day. Open source experimenting. Oh man this thing is really great. Holy cow it’s getting out of hand with all the data we generate and we are using it for so much of our critical uses. Now what?
Elastic is pursuing a strategy of differentiating their Hosted service go a point that the competitor services are laughably under served. If successful the payoff should be huge. AWS Elasticsearch Service was a huge success for AWS growing quite large very quickly because of the reasons we see here. The need to go hosted. But Elastic’s own service will get the bigger share of that going forward I believe. And that’s the investment thesis.
Another great case study is BPCE, France’s second largest financial institution. Which was mentioned in latest call. They now have deployed on Elastic Cloud Enterprise, which is Elasticsearch Service Hosted on Private Cloud instead of the public options. In this study they were a platinum subscriber and mention they intend to go ECE, which they did.
https://www.elastic.co/customers/bpce
Darth