Encrypted transport
Every connection runs over TLS 1.3 / QUIC with channel binding.
- Fallback: TCP-TLS and WebSocket on port 443
Security
We describe what works today and what the goal is — without marketing exaggeration.
Honestly: the system is designed for end-to-end (E2E) encryption, but we do not yet claim it for every channel. Once it is independently verified, we will say so here.
Every connection runs over TLS 1.3 / QUIC with channel binding.
Connections are authorised by short-lived, single-use grants signed by the service with Ed25519.
A new machine joins an account only with an expiring, limited-use code generated in the portal.
The controller identifies with its own key pair; you link it to your account by code pairing with fingerprint check.
While someone is connected, the remote machine shows a notice with a Disconnect button.
Relay servers only forward; they neither store nor inspect session content.
We process only what is needed to operate; the portal uses a single session cookie.
Write to us; reports are handled confidentially and we will get back to you.