Join Beta

Beta opening soon · Free seats included

5 Gbps.
Post-quantum.
Managed by you.

The control plane is a blind relay. We never hold the keys. CNSA 2.0 tunnels that only you can configure.

Engineered in Canada · Deployed at the edge

5.17 Gbps
Encrypted throughput
CNSA 2.0
Full suite
Blind
Control plane
24 h
Message retention

Measured on the same line.

Xeon Silver hardware. Same physical link. Same test methodology. QNyx delivers significantly higher encrypted throughput than current WireGuard-Go.

QNyx (qnx0)

5.17 Gbps
Average over 10 s · 6.02 GB transferred · 916 retr

WireGuard-Go (wg1)

3.94 Gbps
Average over 10 s · 4.58 GB transferred · 606 retr
Raw link
9.06 Gbps
QNyx
5.17 Gbps
WireGuard-Go
3.94 Gbps

Managed by you.
Blind to us.

The API is a pure store-and-forward message board. It only ever sees encrypted blobs. Your ML-DSA-87 private key that signs configurations never leaves your control app.

🔒

End-to-end encrypted

ML-KEM-1024 for key establishment, ML-DSA-87 for identity, AES-256-GCM on every payload. Same suite as the data plane.

👁️

We cannot read or forge

The relay has no visibility into configs. It cannot push a configuration and cannot alter one in transit.

⏱️

24-hour retention

Messages between instances and the control app are held for 24 hours, then permanently deleted.

Control appsigns config with ML-DSA-87
↓ encrypted blob
Xaoc APIstores opaque message
↓ pull
QNyx instanceverifies signature · applies

Keys liveonly on your side
API seesciphertext only

From zero to encrypted tunnel.

Asynchronous by design. Your control app and your instances talk through the relay like a message board.

STEP 01

Sign up

Create an account and receive free QNyx seats for the beta. No credit card required.

STEP 02

Install

Deploy the QNyx instance binary on your Linux hosts (or Android). Generate identity keys locally.

STEP 03

Configure

In the control app, define desired state. It is signed with your private key and posted as an encrypted blob.

STEP 04

Pull & run

Instances asynchronously fetch, verify the signature, and apply the configuration. Tunnel is live.

CNSA 2.0 from the first handshake.

The same post-quantum suite protects both the data plane and the control plane.

Key Establishment

ML-KEM-1024

Post-quantum key encapsulation for shared session material.

Identity & Auth

ML-DSA-87

Digital signatures that bind identity and sign every configuration.

Authenticated Encryption

AES-256-GCM

Protects handshake messages, data-plane traffic, and control payloads.

Free seats on sign-up.

Join the QNyx beta and receive free seats to run managed, post-quantum tunnels. Limited windows. No credit card required.

Trust questions, answered.

Can Xaoc push or alter a configuration?

No. The control plane is a blind relay. It only stores and forwards encrypted blobs. Configurations are signed by your ML-DSA-87 private key, which never leaves your control application.

How does QNyx know who to trust?

Upon first connection with QCore controller, a QNyx instance becomes unable to accept configurations signed by any other key than that of the QCore controller that first connected with it. This is enforced though ML-DSA-87 identity checks.

Where do the private keys live?

Only on your side — in the control app (and on the instances for their own identity keys). Xaoc never holds, sees, or can reconstruct them.

What does the API actually see?

Opaque encrypted messages. Nothing more. The same CNSA 2.0 suite used for transport also protects every control-plane message.

How long are messages retained?

24 hours. After that they are permanently deleted from the relay.

How does the 5.17 Gbps number compare?

On the same Xeon Silver hardware and physical link, QNyx measured 5.17 Gbps encrypted while WireGuard-Go measured 3.94 Gbps. Raw link capacity was approximately 9.06 Gbps.

Is this still 100 % userspace?

Yes. The QNyx data plane remains a compact userspace binary using the host’s standard TUN interface. No custom kernel modules required.