I built this as an open-source platform for running, tracking, and comparing quantum experiments through a web UI, API, CLI, and SDK.
It includes async job execution, experiment/result persistence, provider abstractions, a demo dashboard, and a local development setup with Docker or lightweight local mode.
The goal was to build something more operational than a one-off script or isolated demo: a control-plane style developer platform for quantum experimentation.
It’s still an early-stage project, but the core execution pipeline is working end-to-end. I’d really appreciate feedback on the architecture, developer experience, and whether the problem framing makes sense.
I built this as an open-source platform for running, tracking, and comparing quantum experiments through a web UI, API, CLI, and SDK.
It includes async job execution, experiment/result persistence, provider abstractions, a demo dashboard, and a local development setup with Docker or lightweight local mode.
The goal was to build something more operational than a one-off script or isolated demo: a control-plane style developer platform for quantum experimentation.
It’s still an early-stage project, but the core execution pipeline is working end-to-end. I’d really appreciate feedback on the architecture, developer experience, and whether the problem framing makes sense.