Hey Product Hunt! 👋

I'm Kamil, and inFlows started the way most side projects do: I was tired of what I had.

Every time something went wrong on Azure Service Bus, the loop was the same - open the portal, click through to the queue, peek a message, squint at a JSON blob in a tiny textarea, lose the lock, start over. Debugging a dead-letter queue at 8pm with that workflow is not a good time.

So I built the tool I wanted. inFlows is a native Windows desktop app that connects to a Service Bus namespace and shows you everything at once: queues, topics, subscriptions, message counts, dead letters. From there you can peek messages without consuming them, settle them properly in PeekLock, resubmit or forward what failed, purge what's stale, and compose and send your own payloads when you need to reproduce something.

The feature I use most is Live Flow - a real-time view of messages moving through the bus. It turns "I think the handler isn't picking this up" into something you can just watch happen.

A few things that mattered to me while building it:

Fast. It's a desktop app, not a browser tab. Opening a namespace and paging through messages should feel instant, and it does.
Safe with credentials. Connection strings are encrypted locally with Windows DPAPI, never written in plain text, and never sent anywhere except Azure itself.
Honest about state. PeekLock is respected properly - no accidental message loss because a UI took a shortcut.

inFlows is in closed beta right now, and free while it stabilises. Windows 10/11, single installer, no account required to try it.

I'd genuinely love feedback - especially from people who live in Azure day to day. What's the thing your current tooling still makes painful? That's the next feature.

Kamil.