# Sentry vs GlitchTip

Canonical: https://inetgeek.com/compare/sentry-vs-glitchtip/

Every value below is read from Sentry's and GlitchTip's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Sentry | GlitchTip |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Entry paid plan | $26/month for Team, the cheapest paid plan | $15/month for the 100,000 event plan; $50 for 500,000 and $250 for 3 million |
| Pricing model | A plan fee plus five independent meters — errors, logs, application metrics, tracing spans and session replays — each with its own included amount and its own overage. Logs and metrics overflow at $0.50/GB; extra uptime alerts at $1.00 each. | Flat monthly tiers bought by event ceiling, with a free self-hosted build as the alternative to paying at all |
| Events included | 50,000 errors a month on Team and Business; 5,000 on Free. Errors are one meter of several — logs, spans, replays and uptime monitors are counted and billed separately. | 100,000 events a month on the cheapest paid plan; 1,000 on the free hosted plan. One meter, not several — GlitchTip counts events and nothing else. |
| Retention window | 30-day lookback on Developer, the free plan. Up to 90 days on Team, and up to 90 days plus additional sampled retention on Business. Enterprise is custom. "Up to" is Sentry's own wording — the 90 days is a ceiling, not a guarantee. | 90 days by default when self-hosted, set by GLITCHTIP_RETENTION_DAYS and configurable per data type — events, transactions, logs, uptime checks and files all inherit it, releases keep 365 days. Events move from Postgres to cold storage after 30 days but stay queryable. GlitchTip publishes no retention figure for its hosted plans. |
| Self-hostable | Limited | Supported |

## Where they differ

### Entry paid plan

- Sentry: $26/month for Team, the cheapest paid plan ([source](https://sentry.io/pricing/))
- GlitchTip: $15/month for the 100,000 event plan; $50 for 500,000 and $250 for 3 million ([source](https://glitchtip.com/pricing))

### Pricing model

- Sentry: A plan fee plus five independent meters — errors, logs, application metrics, tracing spans and session replays — each with its own included amount and its own overage. Logs and metrics overflow at $0.50/GB; extra uptime alerts at $1.00 each. ([source](https://sentry.io/pricing/))
- GlitchTip: Flat monthly tiers bought by event ceiling, with a free self-hosted build as the alternative to paying at all ([source](https://glitchtip.com/pricing))

### Events included

- Sentry: 50,000 errors a month on Team and Business; 5,000 on Free. Errors are one meter of several — logs, spans, replays and uptime monitors are counted and billed separately. ([source](https://sentry.io/pricing/))
- GlitchTip: 100,000 events a month on the cheapest paid plan; 1,000 on the free hosted plan. One meter, not several — GlitchTip counts events and nothing else. ([source](https://glitchtip.com/pricing))

### Retention window

- Sentry: 30-day lookback on Developer, the free plan. Up to 90 days on Team, and up to 90 days plus additional sampled retention on Business. Enterprise is custom. "Up to" is Sentry's own wording — the 90 days is a ceiling, not a guarantee. ([source](https://sentry.io/pricing/))
- GlitchTip: 90 days by default when self-hosted, set by GLITCHTIP_RETENTION_DAYS and configurable per data type — events, transactions, logs, uptime checks and files all inherit it, releases keep 365 days. Events move from Postgres to cold storage after 30 days but stay queryable. GlitchTip publishes no retention figure for its hosted plans. ([source](https://glitchtip.com/documentation/install))

### Self-hostable

- Sentry: Limited ([source](https://develop.sentry.dev/self-hosted/))
- GlitchTip: Supported ([source](https://glitchtip.com/pricing))

## Which should you choose?

Pick Sentry if Teams that want tracing, logs, replays and uptime in one place and will pay per meter for it. The tooling is the deepest in the category and the SDK coverage is the widest.

Pick GlitchTip if Anyone who wants Sentry-shaped error tracking without Sentry's bill — the SDKs are compatible, so switching is a DSN change, and self-hosting is free and genuinely supported.

Consider something else: Sentry — Five meters bill independently, so 50,000 errors is not 50,000 units of observability. A team watching cost needs to watch spans and logs too, not just the error count.

Consider something else: GlitchTip — It tracks errors and nothing else. No tracing, no replays, no uptime monitoring, so a team wanting one pane of glass will be assembling it from parts.

## Documented by only one

- When you exceed a cap: Sentry: Billed, not throttled: each meter charges for additional usage beyond the included amount, at a published per-unit rate.
- Session replay: Sentry: Supported

## Questions this comparison answers

**Entry paid plan: Sentry or GlitchTip?**

Sentry: $26/month for Team, the cheapest paid plan
GlitchTip: $15/month for the 100,000 event plan; $50 for 500,000 and $250 for 3 million

**Should I choose Sentry or GlitchTip?**

Pick Sentry if Teams that want tracing, logs, replays and uptime in one place and will pay per meter for it. The tooling is the deepest in the category and the SDK coverage is the widest.
Pick GlitchTip if Anyone who wants Sentry-shaped error tracking without Sentry's bill — the SDKs are compatible, so switching is a DSN change, and self-hosting is free and genuinely supported.