Open source · Encrypted messaging

Privacy is not a feature.

Pitopi enables real-time private chats. Messages are encrypted in your browser before the server relays them, so the server cannot read their contents.

Get Started Free View Source
Relayed
Architecture
E2E
Encrypted
Why Pitopi

Built for privacy.
By design.

Every design decision follows one principle: stay out of the way of your conversations.

End-to-End Encrypted
Messages are encrypted in the browser before they are relayed. The server handles transport, not plaintext chat content.
Real-Time Relay Chat
Socket.IO relays encrypted messages between users in real time. Plaintext is not sent through the server.
Key-Based Auth
No account password, email, or phone number. Your key file is your identity; an optional password can protect the file locally.
Story Sharing
Share image stories that expire after 12 hours, with visibility controls for everyone or selected people.
Encrypted Local History
Optionally keep chat history on this device, encrypted with a key derived from your key file. Disappearing messages are never stored.
Open Source
The source code is available in the repository. Audit it, fork it, and improve it.
How it works

Three steps
to get started.

01

Download your key

Generate a unique cryptographic key file. This 101-byte file is your entire identity. No sign-up form needed.

02

Connect to the network

Upload your key to sign in. You appear in the user list and can see who else is online right now.

03

Start a private session

Click a user, complete the Socket.IO handshake, and start exchanging encrypted messages. Relay in the app, with server-side relaying.

Pitopi application screenshot

Start a private
conversation.

No account. No email. No phone number. Just download a key and you're in.

Open Pitopi