Open-source quantum software

Software for
the quantum era.

Open-source tools for quantum research and post-quantum security. Run them on your own servers, even with no internet, and your experiments and your systems never leave your hands.

Q-LAB  ·  LIVE
MORROW  ·  LIVE
Open source

Nothing hidden.
Nothing locked in.

Every line of Q-Lab and Morrow is public. That matters most for software like ours: it handles unpublished research and the map of your security weaknesses. You shouldn't have to take a vendor's word for what happens to either. With the source, you can check, and so can everyone else.

  • Check it yourself

    Read every line, or have your security team do it, before it touches a single server. An install you run yourself never reports back to us.

  • Free to run, for good

    No licence fee, no seat count, no expiry date. Run it on as many machines as you need.

  • No lock-in

    Your data sits in an ordinary Postgres or SQLite database on your own server. If we disappeared tomorrow, your copy would keep working and you could keep developing it.

  • It stays open

    Morrow is AGPL-3.0: anyone who runs a modified version as an online service must publish their changes. Nobody can quietly turn it into a closed product.

Q-Lab

Self-hosted
Your runs, circuits and results stay on your server. The backend never contacts us, and the SDK sends nothing to us when it points at your own server.
Hosted by us
Hosted at qlab.soqlab.com: your runs are stored on our server and visible only to you and your organisation. Export them, or request their deletion, from the dashboard.

Morrow

Self-hosted
Runs entirely inside your network. Scan results describe your weakest systems, so they never leave it.
Hosted by us
Hosted at morrow.soqlab.com: your organization's scans are stored on our server and visible only to your organization. An account can only scan domains it has verified it controls.

Q-Lab is MIT: use, modify and redistribute it freely, keeping the copyright notice. Morrow is AGPL-3.0: the same freedoms, and anyone who offers a modified Morrow as an online service publishes their changes too. All our code on GitHub ↗

Your data stays yours

AI that works for you,
not on you.

Most AI tools work the same way. Your code, your circuits and the map of your infrastructure go up to someone else's cloud, where an agent you can't inspect reads them, and your prompts may be kept or used to train the next model. For a lab's unpublished results or a company's cryptography, that is exactly the data you can least afford to hand over.

We build the other way round. The code is open, so you can see what it does. It runs inside your own network, offline if you want. And the AI is yours: connect a model on your own hardware, and nothing it reads ever leaves the building. Prefer not to run servers? Our hosted service is there too. Your choice, not ours.

Typical cloud AI toolQ-Lab and Morrow, self-hosted
Where it runsTypicalOn the vendor's cloud.Ours, self-hostedOn your own servers, even on a network with no internet connection.
Where your data goesTypicalTo the vendor, and on to whichever AI company it uses.Ours, self-hostedNowhere. No telemetry, no licence check, no calls home.
The AI modelTypicalTheirs: shared, remote, and closed to inspection.Ours, self-hostedYours: Ollama, vLLM, LM Studio or any OpenAI-compatible server on your own hardware. Or none at all.
Training on your workTypicalDepends on terms you didn't write and can't verify.Ours, self-hostedNot possible. Your data never reaches us in the first place.
Checking the codeTypicalYou take their word for it.Ours, self-hostedRead every line: Q-Lab is MIT, Morrow is AGPL-3.0.
Use cases · Where quantum landsIllustrative visualisation
Quantum research · Q-Lab

Every experiment, on the record.

Research teams run circuits on real quantum hardware today. Q-Lab records each run with its circuit, backend and calibration, so results can be compared, shared and reproduced.

Research

Two frontiers.
One clock.

The machines that will run useful quantum programs are the same machines that will break today's public-key cryptography. We work on both problems.

Quantum computing

Make every quantum result reproducible.

Quantum hardware is real, noisy, and its calibration drifts by the hour. A result is only as trustworthy as the record of how it was produced: the circuit, the backend, the calibration, the code.

Problem
Runs that nobody can reproduce six weeks later
Our work
Q-Lab
Post-quantum security

Find the cryptography quantum will break.

A large enough quantum computer breaks RSA and elliptic-curve cryptography. Traffic recorded today can be decrypted then. The replacements are lattice-based, and the migration starts with knowing what you run.

Standards
NIST FIPS 203, 204 and 205, published 2024
Our work
Morrow
Approach

How we build.

Three rules every SOQLAB product follows, whoever runs it and wherever it runs.

Open source

Open by default

Our products are open source. Read the code, run it yourself, or send a pull request.

Self-hostable

Runs on your infrastructure

Use the hosted version or run it yourself, even on a network with no internet. Experiment data and cryptographic inventories stay where you put them.

Auditable

Evidence over claims

Every Q-Lab run records its circuit, backend, calibration and code, so it can be reproduced. Every Morrow action lands in a hash-chained audit log that shows if anything was altered.

Contact

Building something quantum?
Talk to us.

Pick a topic and we'll draft the email for you. It opens in your own mail app, so nothing is sent until you press send.

Or write directly
New messageDraft
To
contact@soqlab.com
Subject
Self-hosting question
Fill in the [brackets] before sendingOpen in mail app →