Hi, I'm Hauke Jung — a full-stack developer who built Thermite because error trackers were built for a world where a human reads every stack trace.
I spent years watching Sentry issues pile up: hundreds unread, alerts everyone had muted, and a bill that grew with our traffic for a tool one person ever opened. Then coding agents got good enough to read a stack trace, and the tracker was the thing in the way. Thermite is my answer: Sentry's wire protocol, one binary and a Postgres, and an MCP server that hands every new issue to your own agent — AGPL, so you can run it wherever you like.
Hauke Jung
Thermite founder
Thermite is rust and aluminium, and it burns through steel.
Hans Goldschmidt mixed the two in Essen in 1895 and found that once lit, the reaction brings its own oxygen: you cannot smother it, water does not put it out, and it runs at 2,500 °C until the fuel is gone. Railways have welded their rails with it ever since. It is what you reach for when the joint has to hold and nothing gentler will do.
A production error is the same kind of problem. It does not go out because nobody is looking at it; it keeps burning until someone reads the stack trace and finds the line. Thermite is built so that someone is your coding agent, and the diagnosis is on the issue page before you have opened it. The mark is a molten triangle around a white-hot core — a reaction is hottest at its centre, and so is a stack trace. And yes, it is written in Rust. The pun was free.
thermite.
[thur-mite] (iron oxide + aluminium) noun
A mixture that, once lit, cannot be put out. Also: a small error tracker that hands every crash to your coding agent and does not let go until it is diagnosed.
Built for teams whose agent reads the stack trace.
One person, a narrow scope, and a long-term commitment to the people — and the agents — who use it.
Agent first
Every feature starts from one question: does this get a coding agent, or the human reading behind it, from crash to diagnosis faster? If not, it doesn't ship. Thermite never calls a model itself — your agent runs on your machine, under your key.
Rust all the way down
Ingest, grouping, the dashboard, the MCP server and the SDK are one Rust workspace. One binary and a Postgres — no Kafka, no ClickHouse, no dozen containers to keep alive at three in the morning.
Built in the EU, hosted where you say
AGPL-3.0: self-host it anywhere and your stack traces never leave a Postgres you control. The hosted version runs on servers in Germany, GDPR by default, with no tracking cookies and no cookie banner to go with them.
Send me a message
A question, a bug, a Sentry bill you would like to stop paying — write me and I will answer as soon as I can.