Self-Hosted Alternatives to Sentry

Why Replace Sentry?

Sentry’s free tier covers 5,000 errors and 10,000 performance events per month. That’s generous for side projects, but production applications burn through those limits fast. The Team plan starts at $26/month for 50K errors, scaling to $80/month for 100K and higher.

The real issue isn’t the base price — it’s the unpredictability. A single deployment bug can generate thousands of duplicate errors in minutes, spiking your bill or exhausting your quota right when you need error tracking most.

Beyond cost:

• Data sensitivity — Error reports contain stack traces, request payloads, user data, and environment variables. Sending this to a third-party service raises compliance questions for GDPR, HIPAA, and SOC 2 audits.
• SDK lock-in — Sentry’s SDKs are open-source, but many advanced features (session replays, profiling, custom dashboards) only work with Sentry’s cloud. Self-hosted alternatives that accept the same SDKs give you a migration path without rewriting instrumentation.
• Retention control — Sentry cloud retains data per plan limits. Self-hosted, you keep data as long as your disk allows.

Best Alternatives

GlitchTip — Best Overall Replacement

GlitchTip is the lightest path to self-hosted error tracking. It accepts Sentry SDKs — swap the DSN in your existing sentry_sdk.init() call and errors flow to your own server. No code changes beyond the DSN.

GlitchTip also includes built-in uptime monitoring (HTTP, ping, heartbeat checks), which eliminates the need for a separate tool like Uptime Kuma. Runs on Django with PostgreSQL, using under 512 MB of RAM.

Best for: Teams that want Sentry SDK compatibility without Sentry’s infrastructure weight. Small to medium applications.

Trade-offs vs Sentry: No session replays, no profiling, no advanced dashboards. Basic performance monitoring only.

Read our full guide: How to Self-Host GlitchTip

Sentry Self-Hosted — Most Feature-Complete

Sentry itself is open-source (BSL license — free for self-hosting, restrictions on offering it as a service). The self-hosted version includes nearly all cloud features: error tracking, performance monitoring, session replays, cron monitoring, and custom dashboards.

Best for: Teams that need the full Sentry feature set and have the infrastructure to run it. Large applications with high event volume.

Trade-offs: Requires 8+ GB RAM, PostgreSQL, Redis, Kafka, Clickhouse, Snuba, and 20+ Docker containers. Significantly more complex to operate than GlitchTip. Upgrades between versions can be involved.

Highlight.io — Best for Full-Stack Observability

Highlight.io combines error tracking, session replays, log management, and tracing in a single platform. The self-hosted version runs via Docker Compose with Clickhouse for storage.

Best for: Teams that want session replays alongside error tracking. Full-stack observability without separate tools.

Trade-offs: Newer project, smaller community than Sentry. Requires more resources than GlitchTip. Not directly compatible with Sentry SDKs — uses its own SDK.

Migration Guide

From Sentry Cloud to GlitchTip

Migration is straightforward because GlitchTip accepts Sentry SDKs:

1. Deploy GlitchTip (setup guide)
2. Create a project in GlitchTip matching your Sentry project platform
3. Copy the new DSN from GlitchTip
4. Update your application’s Sentry SDK configuration:

Python:

import sentry_sdk
sentry_sdk.init(
    dsn="https://[email protected]/1",  # New GlitchTip DSN
    traces_sample_rate=0.1,
)

JavaScript:

Sentry.init({
  dsn: "https://[email protected]/1",  // New GlitchTip DSN
});

5. Deploy your application — errors now flow to GlitchTip
6. Historical errors from Sentry don’t transfer (there’s no import tool). New errors start accumulating immediately.

From Sentry Cloud to Sentry Self-Hosted

1. Deploy Sentry self-hosted using their official guide
2. Create matching projects and teams
3. Update DSNs in your applications
4. Historical data migration is possible via Sentry’s export/import tools but complex for large datasets

Cost Comparison

Annual costs based on application generating ~100,000 errors/month:

	Sentry Cloud (Team)	Sentry Cloud (Business)	GlitchTip (Self-Hosted)	Sentry (Self-Hosted)
Software	$80/month	$213/month	Free (MIT)	Free (BSL)
Annual cost	$960	$2,556	$0	$0
Server hosting	N/A	N/A	~$120/yr (2 GB VPS)	~$480/yr (8 GB VPS)
Event limit	100K/month	100K/month	Unlimited	Unlimited
Overage cost	~$0.000875/event	~$0.000875/event	N/A	N/A
Total annual	$960+	$2,556+	~$120	~$480

For applications generating 500K+ errors/month (common in production), Sentry cloud costs jump to $300-500/month. Self-hosted GlitchTip stays at the same hosting cost regardless of volume.

What You Give Up

• Session replays — Sentry cloud records user sessions for debugging UI issues. GlitchTip doesn’t have this. Sentry self-hosted does.
• Profiling — Sentry cloud includes continuous profiling for Python, Node.js, and other languages. Not available in GlitchTip.
• Advanced dashboards — Sentry cloud has custom dashboards and discover queries. GlitchTip has basic project-level views.
• Cron monitoring — Sentry tracks scheduled job execution. GlitchTip has uptime monitoring but not cron-specific tracking.
• Managed infrastructure — Sentry cloud handles scaling, backups, and availability. Self-hosted means you own that responsibility.
• Mobile crash reporting — Sentry has mature iOS/Android crash reporting with symbolication. GlitchTip supports it through Sentry SDKs but with less depth.
• Team features — Sentry cloud has issue assignment, routing rules, and ownership rules. GlitchTip has basic team support.

FAQ

Does GlitchTip work with all Sentry SDKs?

GlitchTip supports the Sentry SDK wire protocol for error tracking, breadcrumbs, and basic performance monitoring. Language-specific SDKs (Python, JavaScript, Go, Ruby, Java, PHP, etc.) all work. Advanced features like session replays and profiling are not supported.

Can I run GlitchTip and Sentry side by side during migration?

Yes. Configure your SDK to send to both using the Sentry SDK’s before_send hook or run two SDK instances. In practice, just switching the DSN is simpler — you get immediate coverage on GlitchTip while keeping Sentry active until you’re confident.

How much disk space does self-hosted error tracking need?

GlitchTip uses roughly 30 GB per 1 million events/month (with default 90-day retention). Sentry self-hosted uses more due to Clickhouse and Kafka overhead. Set GLITCHTIP_MAX_EVENT_LIFE_DAYS to control retention.

Is Sentry self-hosted the same as Sentry cloud?

Nearly. Sentry self-hosted includes most features (error tracking, performance, replays, cron monitoring). Some enterprise features (advanced RBAC, SCIM provisioning, single-tenant options) are cloud-only. The self-hosted version uses the BSL license — free for internal use, restrictions on offering it as a commercial service.

Related

• How to Self-Host GlitchTip
• GlitchTip vs Sentry
• How to Self-Host Uptime Kuma
• Best Self-Hosted Helpdesk Software
• Self-Hosted Alternatives to Zendesk
• Docker Compose Basics