Launched PipeRadar — "Sentry for background job queues"

I shipped PipeRadar today after building it nights and weekends. It's monitoring for BullMQ job queues: drop one line into your worker and it groups failed jobs into incidents, tracks latency, and alerts you before your users notice. The origin story is embarrassingly common: a job in my app failed silently for two days and I found out from a customer. Turns out "did a background job just fail?" is a question most teams can't answer quickly. The bet I made: cost has to scale with problems, not traffic. I store failures as rows but fold successes into per-minute rollups, so a high-volume queue doesn't become a storage liability. That's what lets the free tier actually be free instead of a trap. SDK is open source (MIT): github.com/pipe-radar/sdk-bullmq Live + free tier: piperadar.dev Two things I'd love IH's read on: (1) does the free → $29 → $79 laddering feel right, and (2) is "one line in your worker" a strong enough hook, or should I lead with the failure-grouping? Tearing it apart is welcome.