Sentry is a hosted error tracking and application monitoring service whose self-hosted edition is source-available under the Functional Source License; these pages cover replacing Sentry SaaS with open-source GlitchTip.
Sentry SaaS against open-source GlitchTip for error tracking: Sentry SDK compatibility, what GlitchTip covers (errors, performance, uptime, logs) and which Sentry features it does not, the small PostgreSQL footprint, and why FSL-licensed self-hosted Sentry is not the open-source option.
Moving error tracking from Sentry to self-hosted GlitchTip by keeping the Sentry client SDKs and pointing each project's DSN at GlitchTip: project and team setup, alert rules to re-create, running both in parallel, and what history to export from Sentry first.
Cost of ownership by component: Sentry's plan prices and event quotas, retention limits and SSO gating against GlitchTip's PostgreSQL and worker infrastructure, setup, upgrades and on-call time, compared with the hardware self-hosted Sentry would need.
What can be pulled out of Sentry SaaS through its web API: issues, events and project settings, region-specific API hosts, cursor pagination and rate limit headers, and what must be re-created by hand in GlitchTip such as alert rules and integrations.
Why Sentry's EU region does not keep everything in the EU (accounts, tokens, DSN keys and audit logs stay in the US) and cannot be switched after creation, and how self-hosted GlitchTip in an EU data center keeps events and account data under the customer's control.
Before replacing Sentry, some teams self-host it. This page compares Sentry SaaS with self-hosted Sentry under the Functional Source License: hardware needs, features missing when self-hosting, the low-volume positioning of the self-hosted package, and when GlitchTip is the simpler choice.
For teams that want error tracking inside a full observability stack: Sentry's issue grouping and release tracking against SigNoz's OpenTelemetry exceptions, traces, logs and metrics in one self-hosted tool, and where each fits.
Replacing Sentry's session replay with self-hosted OpenReplay: replay alongside console logs, network activity and JavaScript errors, input masking and private mode, and how to keep errors in GlitchTip while replay runs separately.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.