Menu

1 / 2

PostHog Error Tracking Killed My Sentry Bill

DEV Community·RAXXO Studios·6 months ago
#GeD15cIw
#ai#productivity#claudecode#posthog#sentry
Reading 0:00
15s threshold

Sentry cost me 80 EUR/month for ~12k errors that PostHog now catches on the free tier

posthog-js already loaded on the storefront, so error tracking was a 4-line config change

Source maps upload in ~3s through a Vite plugin, stack traces stay readable

Tool count dropped from 2 to 1, and OpenTelemetry handles the gaps PostHog leaves

I was paying 80 EUR/month to Sentry for a one-person studio shipping ~12k errors per month, while PostHog already ran in the same page for analytics and session replay. Once I noticed PostHog had quietly shipped a real Error Tracking product, the math was insulting. One evening later, Sentry was gone and my observability stack was a single SDK.

The Sentry Bill That Stopped Making Sense

I started with Sentry years ago because it was the obvious choice. Errors come in, they get grouped, you fix them, you move on. The Team plan at 80 EUR/month felt fine when I was on a Pro consulting contract.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.