QNetwork™ · Emulated preview
Model a quantum network.
No hardware attached.
QNetwork is the modelling layer of QCOS: a reference listing of backends, a three-node model topology and a trapped-ion configuration sweep. The topology and the sweep are emulated and labelled that way. The rest is reference data.
- Model nodes
- 3
- Configurations scored in a sample sweep
- 36
- Physical quantum links
- 0
Read from the preview API and one sample sweep, not performance claims.
QNetwork models a network. It does not connect to one.
Labelled at the source
Topology and sweep responses say EMULATED. The backend listing carries demo_mode.
Nothing leaves QCOS
No job leaves QCOS through QNetwork, and no call here reaches a quantum computer.
You name the backend
To run a circuit, use QCOS and name the backend for every job. QNetwork does not choose one for you.
Four things you can call today.
Each one is a call to the preview API, shown the way the response labels it.
One call returns the state of the model: three nodes, no pairs held, no calibration, and a mode field that reads emulated.

Network status
status
The emulation service
mode
What answers you
nodes_online
Model nodes
active_pairs
Model pairs held
last_calibration
No calibration recorded
Reference data
Three ion species, side by side.
Coherence times, gate fidelities and gate durations for 171Yb+, 40Ca+ and 43Ca+, served as reference figures. They are not measurements on any machine.

Ion species · two-qubit gate fidelity
171Yb+
T2 1,500 ms · two-qubit gate 200 µs
40Ca+
T2 50 ms · two-qubit gate 50 µs
43Ca+
T2 50 ms · two-qubit gate 100 µs

Model links
The links in the model are numbers.
Each link in the topology carries a technology and a latency. Nothing is spliced, lit or measured. Entanglement, teleportation and remote gates between machines are not offered.
Not in QNetwork Today
Automatic backend selection comes later, and in order: observability first, then measurements, then a corpus of validation records that any selector has to be checked against.
- Automatic backend selection
- Load balancing across backends
- Automatic failover
- Running one circuit on several backends and aggregating the results
- Entanglement, teleportation and remote gates between machines
Tell us what you need from a quantum network
QNetwork is a preview. Tell us the workload you have in mind and we will tell you what runs today and what does not.
Footage: Mk.II Media & Design and Adam Fackelman on Pexels. Photographs: NIST and USDA, public domain. None shows SoftQuantus hardware.