Approve the peer
Hybrid X25519 + ML-KEM-768 key exchange and Ed25519 identities support code-verified pairing with distinct peer secrets.
RESOURCES / SECURITY & ACCESS
Trust each connection.
Authorize each capability.
A security design built around peer approval, explicit roles, authenticated transport, and separate software activation.
SECURITY FOUNDATIONS
Separate identities.
Clear responsibilities.
The software is a preview and has not been presented as an audited production security boundary.
Authenticate the session
Encrypted catalog transport and authenticated QUIC media sessions protect separate workflow paths. Pairing identity is not a hardware license.
Verify your license
ML-DSA-65 signatures authorize a product and device fingerprint. The app embeds a public verification key; signing secrets stay with the authority.
Grant capabilities explicitly
View, input, files, and clipboard permissions are per-peer. Receiver approval and dual opt-in live clipboard keep sharing deliberate.
Keep billing server-side
Sign-in continues to auth.cyberplexs.com. Authentication, billing, and license entitlement belong to that service; the static website does not grant access.
State the boundaries
Local trial files and OS hardware identifiers can be altered by administrators. Online anti-abuse, revocation, and enterprise auditing need the planned service.
Available foundations & preview
What you can explore today.
Hybrid peer pairing, encrypted sharing/catalogs, authenticated media, and device-bound signed-license verification.
Product direction
Where the platform is going.
Independent security review, enterprise identity integration, central auditing, server-backed trial tracking, and published commercial security commitments.
ENCRYPTED IPFS / PLANNED SHARING
Protect contents before publication.
The planned friends-and-family sharing workflow encrypts files before adding them to IPFS and separates recipient decryption access from the content reference. IPFS provides transport encryption, but file contents require their own encryption.
Public content identifiers and node metadata may remain visible. Availability depends on hosting or pinning; revoking an invitation cannot erase copies a recipient already holds. IPFS privacy and encryption guidance ↗
Explore friends & family sharing →