QCOS Quantum Isolation™
An isolation policy for multi-tenant execution on shared quantum hardware. In our Monte Carlo simulation, cross-tenant leakage falls to statistically indistinguishable from random guessing. It has not been validated on a physical device, and QCOS offers no QPU access today.
The problem: multi-tenant QPUs create a physical side-channel
Cloud quantum computing is inherently shared. When different tenants execute on neighboring qubits, crosstalk and timing correlations can create a measurable side-channel. A co-tenant can attempt to infer the class of a victim workload using sensor circuits and statistical learning.
IP Leakage Risk
Algorithms, model structure, and circuit families can be inferred by malicious co-tenants.
Vendor Risk
Tenant isolation is often not quantified in provider documentation.
Compliance Risk
Hard to audit, hard to prove non-disclosure. Regulators require quantified security evidence.
What QCOS Quantum Isolation delivers
Simulation results with auditable evidence, bounded by an explicit threat model.
Quantified in Simulation
In a Monte Carlo simulation of the threat model, attack success falls to random guessing: the Wilson 95% CI includes 50% and the exact binomial test fails to reject p = 0.5.
Auditable Evidence
Tamper-evident Isolation Evidence Bundle per run. Export as JSON and PDF, sealed with a SHA-256 content hash, for security reviews.
Controlled Overhead
Security-utility tradeoffs are explicit. The simulation model assumes 11% qubit overhead, 15% throughput impact and <0.5% fidelity loss; none of these is measured on hardware.
Physical Isolation Model
A layered policy modelled in simulation: topological buffering, layout randomization, temporal decorrelation and decoy injection. Not yet applied to a real multi-tenant QPU.
How it works
A layered isolation strategy targeting the physical leakage channel
Topological Buffering
Topology-aware placement enforces physical distance between tenants to attenuate electromagnetic coupling.
Per-Job Layout Randomization
Qubit mapping changes per execution to prevent cross-run statistical accumulation attacks.
Temporal Decorrelation
Randomized timing and reset barriers reduce synchronization and drift exploitation between tenants.
Active Decoy Injection
Independent decoy workloads reduce side-channel SNR. Generated independently of victim structure, with second-order impact evaluated in simulation.
Isolation tiers
Choose the right balance of security and overhead for your workload
STANDARD
Logical isolation
- Scheduler-level separation
- Basic buffer policy
HIGH
Buffer + temporal gap
- 1-qubit buffer zone
- 100μs scheduling gap
- Reset barriers
MAXIMUM
Verified reset barriers
- 2-qubit buffer zone
- 1ms scheduling gap
- Post-reset verification
EXTREME
Largest simulated reduction
- 3-qubit dynamic buffer
- 5ms temporal gap
- Per-job layout randomization
- Active decoy injection
- Tamper-evident evidence bundle
Who this is for
Built for regulated industries and security-conscious organizations
Financial Services
Protect proprietary trading algorithms and risk models from co-tenant inference attacks.
Government & Defense
Evaluate isolation policies for sensitive workloads on shared quantum infrastructure. No accreditation is claimed.
Pharma & Life Sciences
Reduce the risk of leakage of molecular structures and drug discovery algorithms to competitors.
Hardware Vendors
Evaluate an isolation policy and evidence format for multi-tenant quantum access.
Cloud Platforms
Design quantum service layers around an auditable tenant isolation policy.
Industrial R&D
Protect materials science and optimization IP from inference attacks on shared QPUs.
What we don't claim
Built for procurement-grade credibility. Our claims are bounded by an explicit threat model and measurable metrics.
- No claim of universal physical limits across all architectures
- No claim of "zero leakage" — claims are bounded by explicit threat model
- Metrics come from a Monte Carlo simulation, summarised with Wilson confidence intervals and exact binomial tests
- Four classifier families were tried in simulation; adaptive adversaries on real hardware have not been tested
- Overhead figures are model assumptions, not hardware measurements
- No real multi-tenant QPU has been tested, and QCOS does not offer QPU access today
Request access
Get a security review package or a simulation-based pilot design for your target QPU topology.
Contact: info@softquantus.com•NDA available on request
Download: Executive Brief
A buyer-friendly 1-page summary with risk framing, metrics, and overhead.
Request PDFFor Vendors: OEM Integration
QCOS is designed to sit above your scheduler to provide isolation policies and evidence generation without changing your hardware stack. This has not yet been tested on a vendor stack.
Learn about OEM program