Compare
Belvador vs Bugsink
Both accept Sentry SDKs by changing the DSN. Bugsink focuses on errors and is free to self-host or sold as a managed service. Belvador runs the server for you in your own Hetzner project and covers cron, uptime, SLOs and OpenTelemetry as well as errors.
The short answer#
Both accept Sentry SDK events; switching is a DSN change.
Bugsink focuses on error tracking and is free to self-host, or available as a managed service.
Belvador runs a managed node in your own Hetzner project and covers cron, uptime, SLOs and OpenTelemetry too.
Bugsink runs on any server; Belvador runs on Hetzner Cloud only.
Side by side#
| Belvador | Bugsink | |
|---|---|---|
| What it is | Error tracking with cron, uptime, SLOs and OpenTelemetry traces/logs | Error tracking you self-host or use managed: stack traces with local variables, grouping, alerts |
| SDKs | Sentry SDKs work by changing the DSN; @belvador/* packages wrap the same Sentry engine | Point existing Sentry SDKs at it by changing the DSN |
| Price | Free during the beta; you pay Hetzner for the node (CX23 lists at €5.99/month excl. VAT) | Self-hosted free; managed from free (15k events) to $16 (75k), $50 (600k), $158 (3M) |
| Server size | One CX23 (4 GB RAM), provisioned for you | Guide: a ten-worker setup fits a 2 GiB server |
| License | Hosted service; SDK packages are MIT | PolyForm Shield 1.0.0 (with listed exceptions) |
Bugsink 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 Bugsink is ahead#
Focus. It does error tracking — stack traces with local variables, grouping, alerts — and little else, which keeps it simple to run.
Runs anywhere. Self-hosting is free and not tied to one cloud. Its single-server guide fits a ten-worker setup on a 2 GiB machine.
Readable source. The code is public under PolyForm Shield 1.0.0, with the exceptions listed in its license.
Where Belvador fits better#
Managed, on your server. Belvador creates the node in your Hetzner project, updates it with signed releases, backs it up daily and tests a restore weekly (BYOC on Hetzner).
Monitoring beyond errors. Cron and heartbeat monitors, multi-region uptime checks, SLOs, OpenTelemetry traces and logs (cron, uptime, OpenTelemetry).
Alerting through your channels: Telegram, Slack, email or a signed webhook (alerts).
What Belvador does not do#
Belvador runs only on Hetzner Cloud, and the service is not source-available. If you need either, Bugsink is the better match.
Questions#
Do I need to change code to try Bugsink or Belvador?#
No. Both take events from the Sentry SDK you already use; you change the DSN.
Is the Bugsink pricing here current?#
It is what bugsink.com listed on the date under the table. Follow the source link for today's prices.
Try it on your own Hetzner project
Free during the beta. Hetzner bills the server; Belvador never bills per event.