Sentry poised to capture APM
Sentry
Sentry can take APM share because it enters through the individual developer, not the central IT budget. Its SDK already sits inside the app and catches crashes, so adding traces, replay, and code level performance data turns an existing debugging tool into a broader monitoring product. That gives Sentry a cheaper path into startups and mid market teams than incumbents that usually start with sales led, organization wide observability deals.
-
Sentry built distribution in error tracking first. By 2023 it had about 50,000 paying customers, around $128M ARR, and roughly 70% of revenue from self serve. That means a large installed base is already sending production data through Sentry, which makes upselling APM more like turning on extra workflows than replacing a vendor.
-
The product difference is concrete. Sentry starts with the exact line of code, stack trace, release, and user session tied to a failure. Incumbents like Datadog and New Relic correlate errors with broader logs, metrics, and infrastructure, but often begin from infrastructure dashboards. Sentry is stronger where app teams want to fix a bug fast, especially in web and mobile product teams.
-
The revenue ladder is large. Sentry's legacy customer value was around $1,500 per account, while New Relic was around $58K ACV and Datadog around $78K. If Sentry proves credible for engineering leaders buying APM across teams, each successful expansion can be worth many times more than the original error tracking sale.
The next phase is Sentry moving from a tool engineers adopt on their own to a standard part of the engineering stack that directors and VPs approve across teams. If it keeps bundling more of the day to day debugging workflow into the same SDK and UI, it can keep climbing from developer utility into a real observability platform with much higher spend per customer.