Sentry

Why solos need error monitoring on day one

The failure mode of an indie SaaS is silent errors. A user hits a bug, the page breaks, they shrug and close the tab, and you find out three weeks later when revenue from that signup never materialises. The polite users send an email; the rest just churn. Without monitoring you are operating blind to the most actionable signal in your product.

Sentry's pitch is straightforward: every error in your application gets caught with a full stack trace, the user's browser, the breadcrumbs leading up to the error, and an alert in your inbox. The 30 seconds between a bug happening and you knowing about it is the difference between a hot-fix at 4 PM and a churned user at the end of the month.

What it does well

The stack-trace experience is the headline. With source maps wired up, you get the original source line with five lines of context above and below, the variables in scope, and the chain of breadcrumbs (clicks, navigation, console logs) that led to the error. For most bugs, you can fix them from the Sentry dashboard without reproducing locally.

Session replay is the unexpected bonus. For errors that need user context (state, form data, scroll position), replay shows the actual session leading to the error. The privacy controls are sensible (text and image masking, custom selectors to ignore), so you can run this in production without a GDPR panic.

The SDK is mature everywhere. Next.js, Node, Python, Ruby, mobile native, and the older stacks all have first-class support. Setup is 10 minutes for the basic install, longer for the proper source-map and release-tracking integration but worth doing once.

Where it disappoints

The pricing model bites if you do not pay attention to it. Sentry charges by error volume; a noisy logger or a runaway client-side loop can blow through 5k errors in a few hours. The first time this happens is a learning experience. Set spike protection, configure error sampling for known noisy paths, and check the volume weekly until you trust the limits.

Source-map upload and release-version configuration is more work than the marketing implies. The first integration takes an afternoon to do right. The payoff is enormous (proper stack traces, regression detection), but expect setup friction.

Default notifications are too aggressive. Out of the box you will get alerts for every new error, which means dozens per week for any active app. Tune the alert rules early: alert on new error type, alert on volume spike, alert on regression, but not on every recurrence of a known bug.

What you do not need

If your "app" is a static marketing site with zero JavaScript, you do not need Sentry. The moment you have a form, a checkout, a user account, or any JavaScript that matters, you do.

Verdict

Non-negotiable for any indie SaaS that takes itself seriously. Free tier is plenty for the first year. The Team tier is the right next step when error volume or replay needs outpace the free limits.