type: service
status: active
timestamp: 2026-06-20
tags: [errors, monitoring, sentry, primary]

Sentry

Primary error tracking — 5K events/mo, per-site env toggle

Sentry

Role

Catches uncaught exceptions across every site + the api.oriz.in Hono Worker + every Chrome extension. Replaces GlitchTip as of 2026-06-20 — the user’s reasoning was “Sentry has the best integration with everything”, and the family’s existing never-hit-quotas rule is satisfied by an env-var toggle (see below) rather than a quota-busting log sink.

Free tier

Card / subscription required?

NO. Free-tier sign-up is email-only. No payment method requested. Stays free forever as long as you don’t exceed the monthly cap.

Per-site env-var toggle (the never-hit-quotas pattern)

Every site reads ENABLE_SENTRY=true|false at build time. Default is false — Sentry only initialises when the env-var is explicitly truthy. This keeps low-traffic sites silent and lets us turn Sentry on selectively for the sites currently being debugged or recently deployed. Combined with the 5K/month cap, the toggle prevents a runaway error loop on one site from burning the family-wide budget.

// inside @chirag127/oriz-kit
if (import.meta.env.ENABLE_SENTRY === 'true') {
  Sentry.init({ dsn: import.meta.env.SENTRY_DSN, ... });
}

The toggle is documented under rules/never-hit-quotas. NO R2 logging fallback — R2 costs money and is explicitly rejected as an error sink.

Alternatives

Swap cost

Low — Sentry’s SDK is the de-facto standard. Most “alternatives” are DSN-compatible; swap means changing the DSN env-var.

Why this is our pick

Best integration coverage of any error tracker — Vercel, Cloudflare Workers, Next.js, Vite, Hono, GitHub Actions, Slack, Discord, Linear, Razorpay-via-webhook all have first-party Sentry hooks. The 5K/month cap is fine when paired with the per-site toggle.

Cross-refs


Edit on GitHub · Back to index