Company
About Belvador
Belvador is error tracking and monitoring that stores your data on a server in your own Hetzner project. It started as the tool we needed for our own portfolio of about twenty SaaS apps.
Updated Oct 25, 2026
The short answer#
Belvador is built by Andrew Babo, its founder, who also runs the apps it was first built for.
Event data lives on your server; Belvador's control plane keeps settings and counts.
Belvador follows existing standards (Sentry envelopes, OpenTelemetry, Standard Webhooks) instead of inventing its own.
It is in beta and free while it is.
Why it exists#
Running about twenty SaaS apps meant twenty places where errors could hide, and an error tracker bill that grew with traffic rather than with the work of fixing bugs. We wanted one screen for every app, the data on servers we already paid for, and alerts through our own Telegram and email.
Self-hosting Sentry was the obvious route and too much to run. Belvador is the middle: the server is yours, the operations are ours.
Rules the product follows#
Your data stays on your node. Buffered copies at the edge are sealed to your node's key. Exceptions — uptime results and ping-URL timings — are listed on data protection.
Standards over our own formats. Sentry envelopes and check-ins, OpenTelemetry, W3C Trace Context, Standard Webhooks,
sentry-cli. You can leave with the tools you came with.Say what is missing. Every product and comparison page lists what Belvador does not do.
Numbers with a date. Benchmarks name the machine, the version and the day (benchmarks).
Sensitive actions need a fresh second factor. Connecting cloud tokens, changing roles and deleting nodes ask for your authenticator code (security).
Contact#
Write to hello@belvador.dev. Security reports go to the address on the security page.
How we write the docs, comparisons and blog is on how we write.
Try it on your own Hetzner project
Free during the beta. Hetzner bills the server; Belvador never bills per event.