This is being worked out, but the gist is likely that we end up merging things rather than choosing between them. Pyroscope have driven more of the clients and

This is being worked out, but the gist is likely that we end up merging things rather than choosing between them. Pyroscope have driven more of the clients and have a deeper understanding of the UI — so we'll probably bias towards Pyroscope for those — and Phlare has driven more of the scalable storage and database — so we'll probably bias towards Phlare for the database. Both teams bring different perspectives of the same problem space, and the two products and their teams complement each other well, so we'll figure out how to take the best from each. The biggest win is the people, the Pyroscope people are incredible and they join a few of our best people at Grafana Labs who were already working on Phlare — in doing so they create this high talent density with a strong purpose to make profiling be an essential, easy-to-use and scalable 4th pillar of observability. For me that is the real potential, to amplify the possibilities of both teams and products by bringing them together. (I work at Grafana Labs, check my profile)