Shipping the first alpha version of OpenQase

06/03/2025By David Ryan
Blog
Release

About those quantum computing business cases. I wrote on LinkedIn about my frustration with lacking an open source repository for this kind of information, and mentioned an idea to explore solving this. The feedback was anecdotally in agreement. While that is nothing special in and of itself, it did echo private conversations with peers across the quantum computing industry. Enough that I put a few hours to prototype an approach to tackle this. Here's the alpha release for OpenQase, a community resource for quantum computing use cases.

This is a simple framework that has two key things. One is a repository of quantum computing business cases as published by the various quantum hardware and software vendors. The other is a "learning path" that aims to cross-relate these business cases with the personas, the algorithms, and the industries involved.

This is very much scratching my own itch from my early days at Quantum Brilliance right up to now with OSRG. And not just for myself. Having a resource to point my various (and cross-discipline) team members to is incredibly useful. And moreso if that applies for a public audience in a way that they might choose to navigate.

As chance would have it, I recently drafted up a set of user personas on the side of some work I did for IonQ's developer experience and API product team. And I have a selection of quantum algorithms written up from my "Pocket Guide to Quantum Algorithms" book that I originally wrote for myself (another experience of creating the "missing onboarding guide" I wish I had).

As for the industries content, those I pulled from a quick literature review, a glance though some press releases, and maybe most of all, some time having a good think over a cup of Yokrshire tea.

The result is this alpha version. Here's a couple of technical notes for anyone who might follow along this project.

  • OpenQase is a simple NextJS application that statically renders Markdown source files.
  • Storage and deployment are both (and only) local for now.
  • The point of the stack is to let me explore how to inter-relate content and curate some educational user journeys.

Check it out and drop me a line with any thoughts or feedback (either via email or on my post over on LinkedIn).