Company
We carry the message. We hold nothing.
Kéryx — herald of the gods. His messages were inviolable by divine law. QERYX is the same instrument, rebuilt in mathematics.
Read what we refuse to hold
Encrypted messengers exist because surveillance exists. Surveillance exists because someone decided the people being watched were the product, the threat, or both. QERYX rejects the framing entirely: you are the one we answer to, and the carrier is the channel — never the keeper.
Your plaintext lives on two devices: yours and theirs. The relay moves sealed ciphertext the way a postal service moves sealed envelopes. The server cannot read messages. Breaking a session requires breaking both X25519 and ML-KEM-1024.
What does the relay actually hold?
Group names and descriptions and all content are end-to-end encrypted; the group avatar, the admin and owner identifiers, and the roster of accounts each conversation delivers to are held by the relay for routing. Sender identifiers are stripped from the stored message row (sealed sender), though the relay authenticates the sender at send time and keeps a per-direction pair counter for up to 180 days. Sealed sender covers text-class messages and small payloads: an image, and any voice or video frame over the envelope budget, is delivered on a lane that does name the sender to the relay for as long as the row lives. Undelivered messages queue with routing metadata under a published retention ladder.
That is the honest sentence, caveats included — the qualified version survives an evaluator, and an evaluator is who we write for.
Where does the quantum layer sit?
A session key can additionally be bound to a CHSH-verified, Tsirelson-window-validated Bell-game transcript both peers seed and any auditor can verify — after both peers complete the Entanglement Ceremony; off by default.
The binding layers above the X25519 + ML-KEM-1024 hybrid floor. The classical floor never weakens, and the security bar never depends on the quantum layer.
This is not QKD. Not quantum networking. Not quantum teleportation. We do not violate the no-communication theorem. Above an X25519 + ML-KEM-1024 floor that alone provides confidentiality, a session can fold a Tsirelson-bounded CHSH witness transcript into its key derivation — a deterministic classical co-possession witness, not physical entanglement; security never depends on it.
Start at the engine, never at the app
Most messengers are a body that grew a lock. QERYX began as the engine — ML-KEM-1024 and ML-DSA-87 hybrid with X25519, Q-Ratchet rekeying on every message — and only then grew a body worthy of carrying it. Security here is the foundation, never a feature, because the whole application exists to serve the engine.
The antimatter problem
An engine this reactive annihilates a conventional container. Real antimatter is held in a magnetic trap, in vacuum — never in a jar — because touching any wall is annihilation. A conventional chat architecture is a jar: the interface reaches into cryptographic state, and every wrong touch is a failed decrypt.
So the architecture is the trap: the interface never mutates crypto state directly, every media key derives through Q-Ratchet, and the invariants — stable identity, ratchet ordering, domain separation — are enforced by structure, not by discipline.
Composition over invention
We did not invent new ciphers. We composed the strongest proven primitives — FIPS 203, FIPS 204, RFC 8439 — layered a verifiable measurement above the floor without ever letting security depend on it, and refused every composition mistake the last decade already paid for.
Know why this exists at all
QERYX began with a hard observation from the war in Ukraine: gaps in encrypted messaging cost lives. Centralized identity systems failed people when their operators were compelled to act against them, and surveillance economics put messengers in conflict with the very people they carried.
QERYX is the messenger that should have existed in 2022 — built for everyone, because protection is not a demographic.
Hold us to five refusals
What we will not do.
- We will not ship a downgraded version. The Connection Floor holds: every conversation runs at maximum parameters.
- We will not insert advertising, telemetry, or analytics into the messenger. The carrier reads nothing, so it has nothing to sell.
- We will not depend on a single distribution channel. More than one road to the binary, each listed the day it opens.
- We will not depend on a single time source, DNS authority, or certificate authority. Sovereignty is a design decision — the mission page names each layer and its honest status.
- We will not soften a caveat to win a headline. Every security sentence names a primitive, links an artifact, or states what the system cannot do.
And what we will do
Publish the artifacts — Security Target, protocol drafts, benchmark suites — and keep them current. Ship reproducible builds and publish build attestations. Listen when researchers find issues, fix them, and publish the patches. State what is true today in the present tense, and roadmap as roadmap.
05 / THE SHORT QUESTIONS
Ask the two a stranger asks first.
Why the name QERYX?
Q for the post-quantum core. Kéryx for the herald of the gods, whose messages were inviolable by divine law — intercepting one was sacrilege. QERYX is the post-quantum herald, handed to you.
How do I verify any of this?
Line by line. The Trust Center carries the conformance evidence, and the security overview names every primitive and what a seized relay actually yields.