Nexus Private Chat
Nexus Private Chat is an independent communication project being designed as a complete client-server system for private text, files and future voice communication. The website does not run the messenger; it documents the project and will publish the source code for independent download and compilation.
What is Nexus Private Chat?
Nexus Private Chat is planned as its own communication platform. It is not intended to depend on Matrix, Signal, SimpleX or another messaging network in order to operate.
The project will consist of a Debian server, an Android client and an iPhone client. The objective is to make each component buildable from published source code and to keep server deployment as small and predictable as possible.
Core project goals
The first releases will focus on a small security-oriented foundation rather than a large feature set.
Independent architecture
The server, protocol, client applications, account model and device model are designed as parts of the Nexus Private Chat project.
End-to-end encryption
Private content is intended to be encrypted on user devices so that the server can deliver and store encrypted data without needing the plaintext.
Simple self-hosting
The Debian server is intended to install as a compact native service with minimal runtime dependencies and straightforward administration.
Open-source delivery
Source packages, build instructions, release information and checksums are intended to be published so users can inspect and compile the project themselves.
Security model
The project is designed around device-controlled keys, authenticated encryption, separation between account identity and device identity, and minimization of server-side data. Security will not rely on hiding the source code.
Nexus Private Chat will not invent new cryptographic primitives. The implementation is intended to use established cryptographic libraries and documented constructions. Security claims will be based on the implemented system and later review, not on marketing language created before the software exists.
Target platforms
The same protocol and security model will be implemented across the supported environments.
Debian server
A self-hosted server package for Debian, managed by systemd and designed to avoid unnecessary application servers, message brokers and external database services in the initial architecture.
Android client
A mobile client that can be built from source for Android and connected directly to a Nexus Private Chat server.
iPhone client
A native iOS client built from the published project source using the Apple development toolchain required for iPhone applications.
What the server is intended to do
The server is intended to handle account and device registration, encrypted message delivery, synchronization, encrypted attachment storage, delivery queues and the minimum operational metadata required for the service to work.
The server should not require the private decryption keys used to read end-to-end encrypted conversation content. Some technical metadata will still exist in any practical communication system, so the design goal is data minimization rather than claiming that the server knows nothing.
Planned communication features
These are product goals. Individual features will only be described as available after they are implemented and tested.
1:1 and group messaging
Private conversations, private groups, replies, reactions and device synchronization.
Encrypted attachments
Files, images and voice messages encrypted before upload so the storage service receives encrypted objects.
Message expiration
Configurable disappearing-message policies with deletion of the server copy and application-controlled deletion of local copies.
Voice communication
Private 1:1 calls and later group voice rooms are planned after the core messaging and device-security model is stable.
Open source and independent builds
The public source release is intended to include the server, shared core components, mobile clients, build documentation, security documentation and the license for the release.
Each downloadable source package can be published with a version number and SHA-256 checksum. This page reads that technical release information from one configuration file so release data does not need to be duplicated across every translation.
Project status
Nexus Private Chat is currently in the architecture and implementation-planning stage. The protocol, device trust model, key management, storage format, server package and client build process are being defined before a public production release.
This page is informational. It does not connect to a messaging backend and does not provide a web chat interface.
Source code
Public source packages will be published here for independent inspection, compilation and self-hosting.
Version
0.1.0-dev
Status
Architecture
Release date
Pending
License
Pending
Package
nexus-private-chat-0.1.0-source.zip
Size
Pending
SHA-256
Pending
The first public source package has not been published yet. When it is ready, the download button, package name and checksum will appear here.