agenterr vs sentry
A lightweight, open-source Sentry alternative.
Sentry defined error tracking. Agenterr is for the projects where running it feels like overkill: side projects, solo products, small servers — and the coding agents working on them.
The weight difference
Sentry's own self-hosting docs recommend 16GB of RAM and run a dozen services. Agenterr is one process and one data file, idling around 25MB — it shares a $5 VPS with the apps it monitors.
The pricing difference
Sentry bills per event, so a crash loop can move your invoice. Self-hosting agenterr is free and unlimited under AGPL-3.0, on hardware you already pay for. A hosted option is coming later at a flat monthly price, and it will never bill per event.
The agent difference
Sentry ships an MCP server as an add-on to a product built for dashboards. Agenterr is agent-first: issues, counts, and regressions served over MCP as the primary interface, sized so an agent gets exactly what it needs in one call.
When Sentry is the right choice
A team with real traffic, mobile apps that need symbolication, performance tracing, or an org already on it. Sentry is a deeper product. Agenterr trades that depth for weight, price, and agent access.
 agenterr | Sentry | Datadog | |
|---|---|---|---|
| RAM to run it | ~25MB idle | 16GB+ recommended (self-hosted) | SaaS only |
| Pricing model | free self-host | per-event | per-host + per-GB |
| Self-hosting | one process, one file | a dozen services | not available |
| Agent access | agent-first, MCP built in | MCP add-on | MCP add-on |
| License | AGPL-3.0, free forever | FSL (source-available) | proprietary |