Scarf makes it easy to understand how quickly new versions of Linkerd are being adopted and which components are being deployed—data that the container registries have and don't share with us otherwise.

It's much more popular than we thought. At this stage, we have about 9 million Docker downloads. By monitoring the SDK and game server downloads, we can understand the popularity of different SDKs and the specific uses of the game server, which we couldn't do before. Project observability improves your targeting and allows you to discover new companies for ABM campaigns

It’s important for us to understand who is using [our OSS web framework] IHP. Before using Scarf we’ve mostly relied on the data set of existing customers. . . . It only took us a couple of minutes to integrate the Scarf Gateway. Identify potential customers hidden within your OSS users, creating a new category of leads, Open Source Qualified Leads (OQLs)

Outbound outreach to Open Source Qualified Leads saw 2x higher response rates as compared to our outreach campaigns without Scarf data.

Today, we track over 36,000 users visiting the documentation. We can see those who are very actively engaged in the ongoing process. This helps us reach out to people in those organizations, effectively guiding our outreach process.

I wish I installed [Scarf] the day we launched our docker file.

[We have] been using Scarf to understand how Redpanda is being adopted, and most importantly, how to prioritize engineering efforts for the product. Turns out the world loves Redpanda + Kubernetes more than we thought!

Scarf proved to be a valuable tool for Nestybox ... It’s one of the few tools that we used weekly and considered critical to better understand Nestybox’s users and potential customers.

The list of companies that surfaced from our data in Scarf was important for fundraising to show real-world usage. Showing that big companies were not only downloading Budibase but downloading every new version we released was huge.