Self-hosting error tracking is usually about one of two things: a compliance rule that says telemetry stays inside the network, or a bill that grew faster than the team. GlitchTip and self-hosted Sentry answer that directly. Parsemend answers a narrower version of it (keeping source code and model inference off someone else's servers) without asking you to operate the tracker yourself.
What you actually have to operate
| Sentry (self-hosted) | GlitchTip | Parsemend | |
|---|---|---|---|
| Deployment | Self-hosted (you run it) | Self-hosted (you run it) | Hosted by Parsemend |
| Services to run | Many, incl. Kafka + ClickHouse | Django + Postgres | None |
| Sentry SDKs work | Yes | Yes | Yes |
| Tracing / replay / profiling | Yes | No | No |
| AI fix agent | No (Seer is cloud-only) | No | Yes |
| Agent can run without leaving your network | — | — | Yes, via CLI mode + Ollama |
Self-hosted Sentry
You get the product, all of it, including tracing and session replay. What you also get is the operational surface: this is a distributed system with a message bus and a column store, and the failure modes are the failure modes of a distributed system. Teams who run it successfully usually have someone whose job is partly to run it.
The sharp edge that surprises people in 2026: Seer is not in the self-hosted distribution. If you self-host to keep source code and telemetry inside your network, the AI agent is precisely the feature you cannot have.
GlitchTip
Django and Postgres. It implements Sentry's ingest protocol, does errors and uptime checks, and stops. If your requirement is "error tracking, inside our network, that our existing SDKs can talk to", GlitchTip is the smallest correct answer and you should probably use it.
Parsemend
Parsemend is a hosted service; you don't run it yourself. Events arrive on Sentry's envelope endpoint from the unmodified official SDKs, the same way they'd arrive at Sentry's cloud or any other hosted tracker.
What earns it a place on this page is narrower than full self-hosting. In CLI mode the entire AI fix run happens on the developer's machine: the context bundle is assembled locally, the model call goes wherever you point it, including an Ollama endpoint on your own hardware, and the draft pull request is opened from there. Nothing about that path requires Parsemend to see a line of your source.
That is the one thing neither true self-hosted option on this page can do: self-hosted Sentry has no AI agent in the distribution, and GlitchTip has no AI features at all. It is also the whole reason the four fix modes exist.
The honest limitation
Parsemend has no tracing, no session replay, no profiling and no log ingestion. Self-hosted Sentry has all four. If those are why you self-host, this is not the tool, and no amount of AI makes up for a missing flame graph when you need a flame graph.