Sentry
Sentry is an error tracking and performance monitoring platform that helps developers detect, diagnose, and fix bugs in real-time across web, mobile, and server applications. Developers use it for production error visibility, distributed tracing, performance insights, and AI-powered debugging with Seer.
Overview
| Category | Monitoring |
| Ecosystem | vercel |
| Compliance | SOC2, GDPR, HIPAA, ISO27001 |
| Self-Hostable | Yes |
| On-Prem | Yes |
| Best For | startup, growth, enterprise |
| Last Verified | 2026-02-13 |
Pricing
| Model | tiered |
| Free Tier | 1 user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards
|
| Unit Price | $0 / 1 user |
| Source | pricing page |
Plans
| Plan | Monthly | Yearly | Includes |
|---|---|---|---|
| developer | $0 | $0 | 1 user, Error Monitoring and Tracing, Alerts and notifications via email, 10 custom dashboards |
| team | $26 | $26 | Unlimited users, Third-party integrations, 20 custom dashboards, Seer: AI debugging agent (subscription required), Additional events |
| business | $80 | $80 | Unlimited custom dashboards, Unlimited metric alerts with anomaly detection, Advanced quota management, SAML + SCIM support |
| enterprise | $0 | $0 | Technical account manager, Dedicated customer support |
| Seer AI Debugger | $40 | $480 | Add on to Team, Business, or Enterprise plans, unlimited root cause analysis, automated fixes, and code review on connected repos. |
Strengths & Weaknesses
Strengths:- dx
- reliability
- support
- TypeScript import compatibility with esModuleInterop (default imports fail silently)
- incomplete Bun runtime support (module namespace object binding error, Express instrumentation via Diagnostic Channels)
- OpenTelemetry context propagation issues
- framework auto-instrumentation gaps (e.g., Express with Bun)
When to Use
Best when:- production error tracking
- performance monitoring at scale
- distributed tracing across services
- team-based debugging workflows
- AI-powered root cause analysis with Seer
- mobile app size optimization
- using Bun as primary runtime (incomplete instrumentation, module binding errors)
- strict TypeScript esModuleInterop requirements without workarounds (default imports non-functional)
- need seamless OpenTelemetry integration without manual context management
- TanStack Start projects requiring specialized SDK support
Known Issues (10)
- [high] [JavaScript] TanStack Start SDK
- [high] TypeScript w/ esModuleInterop: `import Sentry from "@sentry/{node|browser}"` is not an error, but does not work.
- [medium] @sentry/bun throws "TypeError: Cannot replace module namespace object's binding with configurable attribute"
- [medium] OpenTelemetry context not propagating
- [medium] Using both Bun and Express leads to "express is not instrumented" warning (Bun not publishing to http Diagnostic Channel)
- [medium] Add support for Cloudflare WorkerEntrypoint
- [medium] Implement Hono SDK
- [medium] Insights: auto-Instrument BullMQ for Queue Insights
- [medium] Capture outgoing HTTP request & response bodies with Node SDK
- [medium] Instrument Cloudflare Worker RPC methods