Last week the payments comparison found two lists that barely overlap: the payments market lists infrastructure, and apps pay with checkout providers. Observability is the opposite case, and the place where it breaks is just as telling. Applications now covers 120 categories and 848 apps, and the apps in 102 of those categories use one or more observability providers: 156 different ones in all.
At the top, the two lists agree. Sentry is in 79 categories and in the Observability market. So are New Relic (24), Bugsnag (21), Datadog (18), Splunk (10), PagerDuty (9), Elastic and Grafana. Sixteen of the market’s 25 members turn up in real apps, against six of 25 in payments.
The miss is the mobile crash reporter. The second most-used observability provider in the apps we track is Crashlytics, part of Firebase, in 59 categories. It is not in the market. Neither are AWS CloudWatch (7), Prometheus (5) or Airbrake (5). The market is drawn around companies whose product is observability. Apps get a large share of theirs bundled inside a platform they already use for something else, and a list of vendors cannot see that.
Five apps still ship Microsoft App Center Crashes, read from their Android builds. Microsoft has since retired App Center. That is the kind of thing a list of vendors will never show you and a list of what apps actually run will.
Every row is graded. Observed rows come from an app’s own code, dependency files or Android build (tracker reports courtesy of Exodus Privacy); declared rows come from its integrations page; inferred rows are never counted. Each provider page now lists the apps that use it, and each category blueprint links the source every row was read from.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.