Catch every error
before your users do.
A focused error tracker for Ruby on Rails teams who deploy on Friday afternoons. Group, resolve, and triage your way out of production fires — without the dashboard sprawl.
Built for Ruby on Rails · Hosted in Europe · Invite only
Everything you need.
Nothing you don't.
Designed for shipping, not for dashboards. Notice the error, find the event, push a fix. No project-management theatre, no AI features that don't actually help you read a stack trace.
Group by fingerprint
Stop drowning in duplicates. One issue, every occurrence — with the timeline of how it spread.
Resolve, ignore, snooze
Ignore rules that match how you actually work: by time, by event count, or by affected-user threshold.
AI tools
Built-in AI assistance that turns raw error data into something actionable — without you copy-pasting a single character.
Terminal mode
An optional 1986 amber-phosphor CRT skin for the whole app. Scanlines, screen-tear glitches, VT323 type. One toggle, full nostalgia.
Uptime monitoring
Periodic HTTP checks alongside the error stream. Same dashboard, same alerting, no second tool to forget about.
N+1 detection
Surface query storms before they hit your bill. Detect, group, and triage performance regressions like real bugs.
Sometimes you just want an amber-phosphor terminal.
Dark mode is fine. Terminal mode is a feeling. Flip one switch and the whole app becomes a 1986 operator station — VT323 type, slow-drifting scanlines, screen-tear glitches between page loads, a warm phosphor halo around every character.
There's something genuinely soothing about reading a stack trace on an amber CRT. Familiar retro shapes calm the eye. The interface stops competing for attention. You stop noticing the dashboard and start fixing the bug.
Toggle it off whenever you like. Or leave it on — we do.
Numbers that matter.
Rendered the right way.
Per-project reports cover what you actually look at on a Monday morning — operational timeline, when errors cluster across the week, what's open by severity, resolve-time distribution, and uptime. Same reports, two skins. Pick the one that suits the moment.
Resolve-time distribution and operational header strip — same numbers, on a CRT.
Request an invite.
We onboard new teams in small batches so support stays tight and the roadmap stays honest. Drop your email and we'll be in touch when the next slot opens.