Since then I left my job and have been building full-time. 400+ organic signups, paying customers across telecom, automotive, and device management. Time for a proper Show HN.

The problem: I've spent 13 years in Android OS internals (AOSP, LineageOS, founding engineer at Esper) and the debugging workflow has never meaningfully improved. You get a 100MB bugreport zip with 20+ files and spend hours ctrl+F'ing timestamps trying to correlate logcat with kernel logs with dumpsys with radio logs. Telecom engineers have it worse because they're also juggling QXDM modem traces. Automotive teams pile VHAL and CAN bus on top of all that.

What logcat.ai does: Upload the files you already have and get a root cause analysis with a correlated timeline across layers (app, framework, HAL, kernel, modem). No SDK, no agents, nothing to install.

How people actually use it: Telecom engineer uploads modem traces alongside a bugreport to figure out why VoLTE calls drop during handovers. MDM company uploads bugreports from fleet devices to triage field issues without reproducing them. Delta mode: upload two bugreports (working vs broken), get a structured diff of what changed without all the noise. Deep Research: autonomous multi-pass investigation that follows causal chains across log sources.

What's interesting technically: The hard part is preprocessing. A 200MB bugreport needs heavy denoising and intelligent chunking before an LLM can reason over it. Every other log type comes with its own challenges and then there is a mix of all of them. We use AI for human readable representation of the analysis and interaction. Currently supports bugreports, logcat, dmesg, tombstones, ANR traces, modem log exports from QXDM/QCAT or Mediatek's/Samsung's modem log outputs.