Q-lab
The missing control panel for quantum developers
Visit Website
August 4, 2026
Q-lab for Quantum circuits deserve better observability
Hey everyone,
Quantum development has a massive blind spot. When you run circuits, you're usually left wrestling with messy logs, opaque outputs, and zero clean way to track how an experiment actually performed over time.
Web developers have advanced observability suites, but quantum devs are still working in the dark.
That is why I built Q-Lab.
It’s a dedicated control panel designed to track, log, and debug quantum circuits cleanly. It replaces the chaos of scattered data with a unified dashboard so you can actually see what your code is doing.
You can check it out here: https://www.soqlab.com/
10 Comments
The observability comparison is interesting because the problem isn’t necessarily running the circuit—it’s understanding what happened after it ran.
That’s a different kind of tooling gap than simply making quantum development easier.
Exactly the gap Q-Lab targets — not running circuits, but understanding what happened after. Automatic experiment logging, run comparisons, parameter tracking across backends. If it's useful, share it with your team or anyone doing quantum work — always looking for early users who get the problem.
Makes sense. The distinction between running experiments and understanding the results afterward is an interesting one.
Hello Aryan,
Manage to run a few experiments? Please feel free to share your feedback and as well sahring it with your peers.
Thank you
I haven’t had a chance to run experiments with it yet, so I wouldn’t want to give you artificial feedback.
I was mainly interested in the distinction you’re exploring — the gap between executing quantum workloads and understanding what happened afterward.
That’s a fair point—I completely agree that artificial feedback isn't useful for either of us.
I’m glad the core problem resonates, though. If you do find yourself running any experiments down the line and end up testing the platform, I’d love to hear your raw thoughts on how it handles the post-execution phase.
And if you happen to know anyone else in your network who is actively struggling with quantum circuit telemetry or debugging, please feel free to share it with them.
Absolutely — I’ll give it a proper test when I get the chance and share my thoughts once I’ve actually run a few experiments.
I’d also be interested in continuing the conversation outside IH. What’s the best email to reach you on?
Thank you very much.
You can find me on linkedIn : Yasseen Nandally
Thanks, Yasseen. I don’t use LinkedIn much, so email would be easier for me.
yasseennandally@gmail.com