Compare
Belvador vs GlitchTip
Both accept Sentry SDKs. GlitchTip is open source under MIT, light enough to self-host on a small server, and also sold as a hosted service. Belvador runs the server for you inside your own Hetzner project and adds cron, uptime, SLOs and OpenTelemetry traces and logs.
The short answer#
Both accept Sentry SDK events; switching is a DSN change.
GlitchTip is MIT-licensed and light enough to self-host on 512 MB with PostgreSQL, or you can use its hosted plans.
Belvador runs a managed node in your own Hetzner project: updates, backups and restores are done for you.
Belvador adds cron monitors, multi-region uptime checks with majority vote, SLOs and OpenTelemetry traces and logs.
GlitchTip runs on any host; Belvador runs on Hetzner Cloud only.
Side by side#
| Belvador | GlitchTip | |
|---|---|---|
| What it is | Error tracking with cron, uptime, SLOs and OpenTelemetry traces/logs | Open-source error tracking with performance and uptime monitoring |
| SDKs | Sentry SDKs work by changing the DSN; @belvador/* packages wrap the same Sentry engine | Works with Sentry's open-source client SDKs |
| Hosted price | Free during the beta; you pay Hetzner for the node (CX23 lists at €5.99/month excl. VAT) | Free 1k events/month; $15 for 100k; $50 for 500k; $250 for 3M |
| Self-hosting | No Docker Compose to run; Belvador applies node updates and backups | PostgreSQL 14+ and one service; 512 MB RAM recommended |
| License | Hosted service; SDK packages are MIT | MIT (backend repository) |
GlitchTip column: from their public pages, read on Oct 25, 2026. Prices and limits change — check the source:
Belvador column, from the docs: What is Belvador, Migrate from Sentry, Quickstart, Connect Hetzner, Choose an SDK.
Where GlitchTip is ahead#
Open source. The backend is MIT. You can audit it and run it on any host, not only Hetzner.
Small footprint. The install guide recommends 512 MB of RAM with PostgreSQL 14 or newer.
Hosted option. If you do not want any server at all, GlitchTip sells hosted plans by event volume.
Where Belvador fits better#
Someone else runs it. Belvador creates the node, applies signed updates, takes daily encrypted backups and tests a restore every week (BYOC on Hetzner).
More than errors. Cron and heartbeat monitors, uptime checks from three regions with majority vote, SLO burn-rate alerts, and OpenTelemetry traces and logs (OpenTelemetry).
Data stays yours even though it is managed: event bodies are stored only on your node (data protection).
What Belvador does not do#
Belvador is not open source as a service, and it only runs on Hetzner Cloud today. If either of those rules it out, GlitchTip is a good fit.
Questions#
Can I switch between them later?#
Both take Sentry SDK events, so switching is a DSN change. Neither imports the other's history.
Is the GlitchTip pricing here current?#
It is what glitchtip.com listed on the date under the table. Check the source link before deciding.
Posts on this topic
All postsTry it on your own Hetzner project
Free during the beta. Hetzner bills the server; Belvador never bills per event.