Compare
Belvador vs Sentry
Both take events from Sentry SDKs. Sentry stores them in its own cloud and prices by plan and volume. Belvador stores them on a node in your Hetzner Cloud project and is free during the beta. Sentry has replay, profiling and AI debugging; Belvador does not.
The short answer#
Both accept events from Sentry SDKs; moving between them is a DSN change.
Sentry stores events in its US or EU cloud and prices by plan and volume.
Belvador stores them on a node in your Hetzner project. It is free during the beta, and Hetzner bills the server.
Sentry has session replay, profiling and Seer. Belvador has none of them. Both have an MCP server for coding agents.
Belvador includes cron monitors, uptime checks and SLOs with no per-monitor price.
Side by side#
| Belvador | Sentry | |
|---|---|---|
| Where your error data lives | On a server in your own Hetzner Cloud project; Belvador provisions and updates it | Sentry's cloud, in the US or the EU region |
| Price | Free during the beta; you pay Hetzner for the node (CX23 lists at €5.99/month excl. VAT) | Developer $0 (one user); Team $29/month; Business $89/month (monthly billing) |
| Included errors | Up to 30 million envelopes per workspace a month; no per-event bill | 5k (Developer), 50k (Team, Business); pay-as-you-go above the reserve, then dropped |
| Retention | Errors 30 days; traces and logs 7 days | 30-day lookback (Developer); up to 90 days (Team, Business) |
| Cron monitoring | Cron/heartbeat monitors (Sentry check-ins or a ping URL), up to 100 per project | One cron monitor and one uptime monitor on every plan; more are billed |
| Session replay, profiling | No session replay | Session replay; continuous and UI profiling (pay-as-you-go) |
| AI and agent access | No AI root-cause analysis; an MCP server (remote with OAuth, or local) lets your own agent read issues, traces, logs and monitors | Seer AI debugging agent ($40 per active contributor/month) and a hosted MCP server |
Sentry column: from their public pages, read on Oct 25, 2026. Prices and limits change — check the source:
Belvador column, from the docs: Data protection, Quickstart, Node health, What monitors are, Capability table, MCP for AI agents.
What Belvador does not do (and Sentry does)#
Breadth. Session replay, continuous and UI profiling, user feedback widgets and a large integration catalogue. Belvador has none of these today.
AI. Seer, Sentry's debugging agent. Belvador has no AI of its own; its MCP server lets the agent you already use read issues, traces and logs.
Nothing to own. Sentry needs no cloud account of yours. Belvador needs a Hetzner account with a payment method, even though it runs the server for you.
Maturity. Sentry has run error tracking at scale for years. Belvador is in beta.
Where Belvador fits better#
Data location. Event bodies, stack traces and attachments are stored only on your node; Cloudflare holds a copy sealed to your node's key only while the node is unreachable (data protection).
Cost shape. No per-event or per-monitor price. The node is a fixed Hetzner server (pricing).
Monitors in one place. Cron and heartbeat monitors, uptime checks from three regions and SLO burn-rate alerts are part of the same workspace (cron, uptime).
Your senders. Alerts go through your own Telegram bot, Slack webhook, mailbox or a signed webhook (alerts).
Moving from Sentry#
Change the DSN; for React, TanStack Start and Cloudflare Workers, switch the import to the @belvador/* package. History is not imported, so keep Sentry read-only for a while. The step-by-step guide is migrate from Sentry, and the overview is on Sentry alternative.
Questions#
Does Belvador work with my Sentry SDK version?#
Belvador accepts Sentry's envelope format. Its own packages pin Sentry's JavaScript engine 10.76.2; for other runtimes, the official SDK with a Belvador DSN is the supported setup (capabilities).
Are the Sentry prices on this page current?#
They are what Sentry's pricing pages said on the date shown under the table. Sentry changes plans from time to time; follow the source links before deciding.
Posts on this topic
All posts- Sentry Seer or a coding agent: who should find the root cause?Sentry Seer or Claude Code and Cursor for root causes: what each reads, price, self-hosting, and what a coding agent does with a wrong AI analysis.
- Sentry MCP or a pasted error packet: what to give a coding agentWhen to connect Sentry MCP to a coding agent and when to paste an error packet: what each exposes, token cost in our test, write access and setup.
Try it on your own Hetzner project
Free during the beta. Hetzner bills the server; Belvador never bills per event.