Skip to content

QShield by Qtonic Quantum Corp. · Protect

Protect the connection. Inspect the proof.

QShield by Qtonic Quantum Corp. protects the connection between systems with post-quantum key establishment and no classical fallback. The evidence behind each claim is published so a reviewer can check it.

Inspect the proofRequest an assessment
Historical record, 28 Sep 2026. Bright marks: confirmed cities in that signed record. Lines: logical connections between paired cities.
Evidence statusPublished record

Published record

Company-published, not independently verified.

  • Key establishment: ML-KEM-1024 (FIPS 203)
  • Endpoint authentication: ML-DSA-87 (FIPS 204)
  • Classical fallback: none
  • Completed endurance run · two hosts · finished 2026-09-16
  • Three days. 4,107 checks. Zero failures.
  • QShield by Qtonic Quantum Corp. runs a locked post-quantum suite between its nodes: ML-KEM-1024 key establishment, ML-DSA-87 signatures, AES-256-GCM; locked profile, no classical fallback.

Live network

Reading the location feed

Historical · Signed record · 50 cities and regions

482 observations over 50 hours, each listing all 50 cities and regions · first and latest signed with the published key of QShield by Qtonic Quantum Corp. · through

Inspect the signed record →

Summary of the published, signed records, each with its date.

The decision

Which connections carry data that must stay confidential for years, and can they be protected now, before a full migration is complete?

Soak status

The qualifying soak has not started. It starts when all 50 locations run the same signed release and pass a verified health check together, and its clock appears here from that signed start record.

The target is 10,000 elapsed hours from a qualifying signed start. The separate 10,000 node-hour requirement remains: 50 locations meeting those start conditions for 200 hours each. Earlier runs are listed below as dated historical records.

Live figures appear only after a verified read of the signed clock file and the location feed; when a read does not return a current projection, its figures clear and this notice says so.

Harvest now, decrypt later

Intellectual property, research, financial records and government communications often need to remain confidential long after transmission. Adversaries can record encrypted traffic today and hold it for decryption by a sufficiently capable quantum computer. Every month of delay adds to what is exposed.

For traffic inside its protected boundary, QShield by Qtonic Quantum Corp. uses ML-KEM-1024 instead of RSA or elliptic-curve key exchange to address harvest-now-decrypt-later exposure.

If required security conditions cannot be held, protected traffic stops. There is no weaker fallback.

QShield by Qtonic Quantum Corp. addresses that exposure for traffic routed through its protected path. A full post-quantum migration takes years. QShield lets an organization protect its most sensitive connections now, on the infrastructure it already runs, while that migration proceeds.

What this does and does not do

Protects
Connections between enrolled Linux hosts inside the protected boundary of QShield by Qtonic Quantum Corp. (S29SP-1 packet protocol; ML-KEM-1024 / ML-DSA-87 / AES-256-GCM).
Requires
Linux hosts you already run, delivered through paid, operator-led engagements. Fail-closed: if required security conditions cannot be held, protected traffic stops.
Does not
Protect traffic outside the protected path, prevent an adversary from recording traffic, or recover data recorded before protection began.
Request a scoped evaluation

Guided product demonstration

Inspect the record behind each state.

Every frame is labeled by evidence state, explains the decision it supports, and links to the method or public sample behind it.

QShield by Qtonic Quantum Corp. outcomes

Decide which connections to protect now, before the migration is complete

01

Post-quantum protected connections

ML-KEM-1024 key establishment and ML-DSA-87 endpoint authentication protect traffic inside the protected boundary. If required conditions cannot be held, protected traffic stops. There is no weaker fallback.

02

Keys stay on your endpoints

Private keys are held on the endpoints. No third party, including Qtonic Quantum Corp, has access to them.

03

Evidence you can inspect

Run logs, state receipts, a verifier, and a SHA-256 manifest are published, so a reviewer can check the record instead of trusting the page.

Why QShield by Qtonic Quantum Corp.

Post-quantum protection with evidence a reviewer can rerun

A completed 72-hour endurance run

Two Linux hosts in separate Oregon availability zones ran for 72 hours between September 13 and 16, 2026 (259,219 seconds on the run's monotonic clock): 4,107 checks, zero failures, and 11 of 11 verifier checks confirmed.

Inspect the endurance evidence

50 locations, one verifiable record

From September 26 to 28, 2026, the 50-location network recorded 482 observations over 50 hours. Each lists all 50 locations and is recorded with its SHA-256; the first and latest are signed with the published key of QShield by Qtonic Quantum Corp., and ssh-keygen verifies them.

Inspect the signed record

Software only

The demonstrated configuration runs as software on Linux hosts, with no hardware changes. Endurance results apply to the identified build.

Operating method

Three steps to a scoped evaluation

  1. 01

    Choose one connection

    Bring a confidential transfer or a link between locations that matters to the mission or the business.

  2. 02

    Define the evaluation

    Your team and ours set the scope, key custody, and success criteria before anything runs.

  3. 03

    Inspect the result

    The evaluation is judged on evidence: logs, state receipts, and checks your team can rerun.

Proof receipt

The completed endurance run and its published record, claim to limitation

Bounded product truth. No customer telemetry in this public view.

Claim
QShield by Qtonic Quantum Corp. completed a 72-hour post-quantum endurance run with published evidence a reviewer can check.
Scope
Two AWS Linux hosts in separate Oregon availability zones, September 13 to 16, 2026.
Method
Download the run log, state receipts, and verifier; rerun every check and compare the SHA-256 manifest.
Artifact
Run log · state receipts · verifier · SHA-256 manifest
Freshness
Sealed record: 2026-09-13 04:28:48 UTC to 2026-09-16 04:29:04 UTC.
Status
completed
Limitation
Results apply to the identified build. QShield by Qtonic Quantum Corp. is not represented as FIPS 140-3 validated or as holding Government authorization.
Inspect the endurance evidenceRead the announcementInspect the 50-location signed record

Governed intake

Evaluation is scoped, never self-serve.

Bring one connection that matters. Your team and ours define the scope, key custody, and success criteria before a guided evaluation begins.

Bring a confidential transfer or a link between locations. Evaluation terms are agreed with your team; nothing is self-serve.

Request a scoped evaluationInspect the evidence