I wanted jq with memory, time ranges, and filters. So I built logdive

Your app is in production. Something broke at 2am. Your options are: grep through a rotated log file, squinting at terminal output. Chain together half a dozen jq pipes until the command line becomes unreadable. Page an SRE to query your observability stack, assuming you have one. Spin up Loki or Elastic locally, spend two hours on config, and then do the actual investigation. All four of these suck. Either you're limited to flat text tooling, or you're paying for infrastructure complexity you d