Conversations have a new address.
Messaging, communities, and voice in one modern communication workspace.
AetherComms brings the conversations you care about into one beautifully simple interface. Join a community, message a friend, or start a voice call — without special receivers, radio equipment, or hardware beyond your everyday device.
Instead of browsing websites, move between conversations with addresses like comms://channel/general or comms://peer/alex in the app's own address bar.
- Message in real time. Keep up with people and conversations across channels.
- Talk privately. Send browser-encrypted direct messages between supported single-device identities.
- Call with your voice. Make one-to-one browser-based audio calls with WebRTC.
- Discover your space. Explore channels, see online presence, and navigate with familiar addresses.
- Move between screens. Use the responsive interface on desktop and mobile browsers.
AetherComms is currently in development; there is no verified public deployment link yet. The README will link to the live app after its frontend and messaging backend are deployed and tested together.
You'll need Node.js 20.19 or newer.
git clone https://github.com/theworker02/aethercomms.git
cd aethercomms
npm install
npm run dev:allOpen http://localhost:5173 and create an account. To test conversations, sign into a second account using a different browser or browser profile.
| Interface | React, TypeScript, Vite |
| Messaging | Node.js and WebSockets |
| Voice | WebRTC |
| Private messages | ECDH P-256 and AES-GCM in the browser |
| Brand | Official logo · Wordmark |
Security note: This is an early-stage project, not an audited secure messenger. Public channels are not end-to-end encrypted. Direct-message keys are tied to local browser storage and aren't verified independently; losing storage may make older messages unreadable. Audio calls may require TURN connectivity on restricted networks. Do not rely on this release for sensitive communications.
Want to contribute or self-host? See the deployment guide, explore the source, or open an issue. You can run checks with npm test and npm run build.