Relay, not archive
Nodes match anonymous routes and forward opaque signaling. If a peer drops offline, sealed payloads wait in volatile RAM for at most five minutes.
NYXPEER
No public signup. No central message archive. One trusted invite opens the door.
Use your invite
Direct route
Peer online
9:41● ●
NyxPeer Private route online
•••M
MaraRoute verified
D
Dev room4 peers · encrypted group
A
AlexEncrypted on device
▰Chats◡Calls✦Settings
Node storage
RAM · 5 min
01 / NODEUS-EAST ONLINE
02 / PROTOCOLWSS + E2EE
03 / RELEASEANDROID 0.8.2
04 / STORAGEZERO SERVER HISTORY
Private communication should feel normal.
Fast enough to disappear.
Private enough to trust.
NyxPeer connects people without turning conversations into a product. Your device owns identity, contacts, and history. Nodes retain only live routes and sealed offline envelopes in RAM for up to five minutes.
NO PHONE NUMBER✦NO MESSAGE ARCHIVE✦NO AD PROFILE✦END-TO-END ENCRYPTED✦
✦✦✦✦
01 / NETWORK
Small server footprint.
Small server footprint.
Large privacy boundary.
Keys stay local
Android Keystore protects app identity. SQLCipher protects local history.
Zero message history
Restart a node. Active routes and queued ciphertext vanish. Conversation history remains yours.
02 / ACCESS
Invited by a peer?
Each NyxPeer member receives a limited set of one-time invites. Enter yours to unlock the signed Android APK.
Redeem invite
03 / START
From invite to private route.
- 01
Get invited
A friend creates a one-time code inside NyxPeer.
- 02
Install signed APK
Redeem code here. Verify signature. Sideload on Android.
- 03
Add your peers
Exchange private contact routes. Start talking directly.
04 / QUESTIONS
Sensible questions.
Sensible questions.
Straight answers.
Why invite-only?+
Controlled growth limits abuse while NyxPeer is early. Existing users decide who joins next.
Is NyxPeer on Google Play?+
Not yet. Current releases are signed APKs. Android verifies future updates against the same release key.
What does a node see?+
Source IP, connection timing, anonymous route IDs, encrypted payload size, signal targets, expiry time, and an opted-in Firebase delivery ID. Never plaintext, private keys, contact names, group details, or readable history.
What if a peer is offline?+
The node keeps the end-to-end encrypted payload in RAM for up to five minutes and sends an opaque wake through FCM. The app fetches and decrypts locally. Expiry or node restart deletes queued ciphertext.
What does Google receive?+
An opaque wake signal only. No message, sender, route, contact, group, call, or ciphertext data. Google can still observe push timing and device/network metadata inherent to FCM.
How do calls connect?+
Encrypted call setup travels through the node. WebRTC sends DTLS-SRTP voice and video directly between peers. Small group calls use an encrypted peer mesh. Calls are disabled in Tor mode because direct media exposes peer IP addresses.