How it works

Hybrid by design. Quantum only where it earns its place.

Proprietary methods decide which part of your problem needs a quantum processor and which does not. Here is the workflow in plain language; the methods themselves stay ours.

The workflow

From your decision to a verdict you can defend

1 · FrameThe decision and thecost of being wrong2 · FormulateModel, screen andclassical baseline3 · Run hybridCPU · GPU · QPU,each where it fits4 · VerdictAnswer, baseline,status, conditionsYour data stays in your perimeter · only abstracted circuit descriptions reach hardware providers

1 · Frame the decision

What are you choosing between, and what does a wrong choice cost? We start from the decision, not the hardware.

2 · Formulate and screen

We turn the decision into a model and screen it: classical, contested or quantum. If classical wins, we say so and stop. The free check runs this screen in about a second.

3 · Run hybrid

CPUs give exact references wherever they can be reached, GPUs carry training and ranking, and the quantum processor runs only the part that is hard classically.

4 · Deliver the verdict with its evidence

You receive the answer, the baseline it was checked against, its status (hardware, computation or projection) and its conditions. The protocol is frozen before the run.

The compute stack

Each processor does what it is best at

CPUExact reference answers wherever they can be reached; sets up the problemGPUTrains and ranks; most of the compute bill lives here, in minutesQPURuns only the part that is hard classically

What stays in your perimeter

The heavy computation runs inside your network or in UAE-resident infrastructure. Only abstracted circuit descriptions reach hardware providers: no raw data, no labels, no business context.

Still from the Merlin Quantum film: transmission towers at dusk

What makes the results hold

Built for the machines that exist today

Constant-depth circuits

Our circuits keep the same depth at any simulated time and any qubit count, so results survive on today's hardware. 126 qubits ran in a single run. Not error-free: designed to hold up under real noise.

Readout that measures the machine

Our readout extracts a processor's own clock to three parts in a hundred thousand and pinpoints which qubit is losing information, so you know which part of the machine is failing your problem.

Cleaner energies on the same chip

By reading frequencies instead of averaging totals, we obtain tighter energies than the standard estimator on the same chip and in the same run.

Still from the Merlin Quantum film: an operations room
Still from the Merlin Quantum film: rack hardware close up

Decide before you build.

Bring us the decision you have to make next.

We tell you which option wins, and whether quantum is the reason.

No keyNo cardAn answer in about a second