Features / Causality
Causality, not log soup.
The backend does the interpreting, so the dashboard shows you the story instead of a raw stream you have to reassemble by hand.
What the backend derives
The raw stream, interpreted.
Queries are normalized into fingerprints, N+1 clusters detected and collapsed, every failed trace carries its immediate cause, and each request links back to what the same user did before it.
One user's journey: every request they made, the jobs and sockets their actions touched, in order, grouped by day.
One query fingerprint: 3,880 calls, the exact line of your code that emits it, the routes it fires from and the traces it appeared in.
And what it leaves alone
Raw values stay raw.
Captured code, paths, SQL and identifiers are stored verbatim. Unravel interprets the structure around your data. It never normalizes or rewrites the developer-written text you need to recognize a problem.
Secrets are scrubbed and oversized payloads truncated before anything leaves your server, but the text you wrote stays exactly as you wrote it. Security & privacy →
Keep exploring
The rest of the toolkit.
Point your AI agent at production.
Connect Claude Code over MCP and it reads the whole causal chain itself, then ships the fix based on what production actually did.
ExploreAsync firstAsync is where PHP apps break.
Websockets, queued jobs and scheduled work are traced like requests, with their own queries, failures and timing.
ExploreAlertingKnow before your users do.
Rules on new exceptions and error spikes, delivered to Slack, email or webhook with the debugging context inline.
ExploreStop reconstructing incidents from logs.
Connect your real app in two minutes. Free forever on a 3-day window, the full debugger included.
Start free