WEBSITE
INTEGRATED
Product, security, download, and account-gated web-client pages now live inside the Nexus Web design and navigation system.
NEXUS WEB // SECURE CHANNEL // FOUNDATION BUILD
TALK LIKE
THE DOOR
MATTERS.
A native desktop client and a separate browser client for one Matrix network. We build the experience and infrastructure around established end-to-end encryption instead of inventing our own cryptography.
Development notice: the Sydney Matrix homeserver and HTTPS endpoint are now online. Trusted-device recovery, signed releases, full real-world integration tests, backup drills, abuse/load testing, and independent security review are still required before a production-security claim.
Message #general… ↗
WHAT EXISTS NOW
REAL SOURCE.
HONEST STATUS.
The source package has a Rust/Iced desktop client, TypeScript web client, Matrix login and E2EE initialization, rooms, timelines, text sending, and server deployment templates.
WEB CLIENT
FOUNDATION
Matrix rooms, encrypted-client setup, timeline sync, text messages, replies, and the shared Nexus Web account gate are implemented.
DESKTOP
SOURCE BUILD
The native Rust/Iced source exists. A signed, tested Windows installer has not been published yet.
NETWORK
LIVE FOUNDATION
The Australian Matrix VPS, PostgreSQL, HTTPS endpoint, and nexweb.site delegation are deployed. Recovery, backup drills, device verification, load/abuse testing, and independent security review are still outstanding.
ONE NETWORK // DIFFERENT CLIENTS
NOT A WEBSITE
IN AN APP COSTUME.
NEXUS WEB
Public pages, account gate, web client, release notes, and future signed download metadata on cPanel.
MATRIX VPS
Synapse, PostgreSQL, encrypted media, restricted administration, monitoring, and backups on a separately controlled server.
NATIVE CLIENT
Rust, Iced, Matrix Rust SDK, and an encrypted local Matrix store. No embedded browser wrapper.
THE SECURITY LINE
NO MASTER
DECRYPT BUTTON.
End-to-end encryption protects message content, not every piece of metadata. A password reset must not be advertised as restoring encrypted history when no trusted device or recovery key exists.
Matrix E2EE remains the cryptographic foundation. Secure Channel does not create a custom message-encryption protocol.
Each installation or browser is a Matrix device. Trusted-device verification and recovery are required before a strong recovery claim.
Public automatic updates stay off until packages and manifests can be signed and verified independently of the website.