Product Thumbnail

Luzo

Design and debug API workflows visually

API
Developer Tools
Artificial Intelligence
GitHub

Hunted byJanarthanan SundaramoorthyJanarthanan Sundaramoorthy

Luzo is a desktop-first, open-source tool for building, running, and debugging multi-step API workflows. Instead of treating requests as isolated calls, it lets you design dependency-aware flows, pass variables between steps, inspect execution through a live timeline, and retry from failure without restarting everything. Built for developers and QA teams working with real API workflows, not just single requests.

Top comment

Hey everyone, excited to share Luzo today. I started building it because I kept feeling that most API tools work well for single requests, but become much less helpful once the work turns into an actual flow. The moment you need to chain requests, reuse variables from previous responses, understand dependencies, or debug failures step by step, the experience gets much more fragmented than it should be. Luzo is my attempt to make that workflow layer feel more natural. I wanted something that lets you design API flows visually, see how data moves between steps, and inspect execution as it happens instead of piecing everything together from logs. I’d especially love feedback on three things: whether the workflow model feels intuitive, whether the execution timeline helps with debugging, and whether the desktop-first direction makes sense for this kind of tool. Thanks a lot for checking it out. I’d genuinely love to hear what you think.

Comment highlights

Visualizing API dependency chains is something I've needed for a while.

When you have Celery workers chaining async tasks,

debugging which call broke the sequence is painful without a visual map.

How do you handle dependent calls where step 3 depends on

the response shape of step 1? Does Luzo let you define

conditional branching based on response validation?

Luzo making API workflows visual instead of cURL-heavy is the right call. The real test will be auth flows and rate-limited responses, since those never behave the same in staging as they do in production.

How does the live execution timeline work when you have parallel branches in a flow, does it show all steps running simultaneously or queue them visually? Congrats on the launch!

Hi fellow hunter! I'm also launching today (Mokkit), just checked out your product

Such a cool idea, it changes from all the AI and agent launches, I wish you success and upvoted you!