// END-TO-END ENCRYPTED · PEER-TO-PEER · ZERO SERVERS

Your data never
touches our servers.

> Not even for a second._

hooly — protocol

$ hooly --info

type : P2P encrypted messenger

transfer : device → device // like torrents, but encrypted

stored : 0 bytes // now. tomorrow. forever.

crypto : X3DH + Double Ratchet

register : none // no phone. no email. just keys.

file_limit: unlimited // P2P has no ceiling

$ _

/** Not just encrypted. Serverless. */

Other messengers encrypt then store on their servers. We don't store anything. Period.

// 01

encrypt(msg)

Encrypted on your device. Never leaves unencrypted.

// 02

notify(peer)

Server sends ONE signal: "delivery pending". That's ALL it knows.

// 03

p2p.connect()

Devices connect directly. Like torrents, but encrypted.

// 04

return 0;

Delivered. Zero trace. Even we can't read it.

// Without internet — mesh mode:

Alice → encrypt → BLE/Wi-Fi Direct → nearby peer → hop → hop → Bob

// Even works days later via store-carry-forward (DTN)

// others.server.storage

+ Your messages

+ Your files and photos

+ Who you talk to and when

+ Your phone number

+ Your IP address

+ Message metadata

+ Group memberships

+ Online status history

// hooly.server.storage

0

null // literally nothing

* One thing: a hashed push token. It doesn't know who you are or what you send.

/* diff hooly others */

HoolyTelegramWhatsAppSignal
Data on servers0 byteseverythingmessages≤30 days
Files on serversneverall filesall filesrelay stored
Data transferP2P directvia serversvia serversvia servers
E2E encryptionalwayssecret onlyalwaysalways
Registrationkeypair onlyphonephonephone
Metadatazerofullfullminimal
If server hackednothing to stealall your datamessages+metasome metadata
File size limitunlimited2 GB2 GB100 MB
Offline meshBLE + Wi-Fi Directnonono
Post-quantumPQXDH (ML-KEM)nonoPQXDH
Phone requiredno — keypairyesyesyes
Max group size200,000200,0001,0241,000
Group callsup to 8 P2Punlimited3250
StoriesP2P (no server)server-basedserver-basedno
Bot platformP2P bots (E2E)server APIbusiness onlyno
DesktopmacOS+Win+Linuxall platformsmacOS+WinElectron

/** Why others fail */

Honest analysis. No marketing. Just code.

// telegram.analysis()

status : NOT encrypted by default

server : stores EVERYTHING forever

data : messages, files, contacts, metadata, IP

register: phone number required

// "cloud messenger pretending to be secure"

// signal.analysis()

status : gold standard E2E

server : relay stores messages ≤30 days

data : phone required, minimal metadata

register: phone number required

// "best of centralized, still centralized"

// keet.analysis()

status : true P2P

server : zero

problem : push notifications BROKEN

problem : offline delivery BROKEN

// "right idea, broken execution"

// hooly.analysis()

status : true P2P ✓ + working notifications

server : ZERO bytes

delivery: silent push wake-up

offline : mesh network (BLE + Wi-Fi Direct)

crypto : post-quantum PQXDH (ML-KEM-768)

identity: Hooly ID — no phone, no email

calls : P2P voice + video + group (up to 8)

UX : telegram-like

// "P2P that actually works"

🔐 class DoubleRatchet

X3DH + Double Ratchet. Forward secrecy — past messages safe even if keys compromised.

🔗 class P2PTransfer

WebRTC direct. Messages, files, photos — device-to-device. Server is just a doorbell.

🔑 class KeypairIdentity

No phone. No email. Cryptographic keypair + 12-word seed. Nobody can ban math.

💨 class DisappearingMsg

Timer self-destruct. Data overwritten with zeros. Secure wipe. Gone means gone.

👥 class GroupEncryption

Sender Keys. Up to 200,000 members. Lazy rotation. Remove someone — all keys rotate. Zero access.

📦 class FileTransfer

50KB or 50GB — no limit. P2P chunked + resume. Server sees zero bytes of your files.

🕸️ class MeshNetwork

Works WITHOUT internet. BLE + Wi-Fi Direct mesh. Multi-hop relay through nearby devices. Messages travel through peers — even offline.

⚛️ class PostQuantum

PQXDH: X3DH + ML-KEM-768 (Kyber). Quantum computers can't break what they can't crack. Hybrid — protected today AND tomorrow.

🪪 class HoolyID

Your address: Nick@123-456-789. No phone number. Dictate it in 18 seconds. Generated from your key — no server involved.

📡 class NearbyRadar

Find people nearby via Bluetooth. No QR needed. No GPS tracked. Just tap and connect. Works without internet.

📹 class VideoCall

P2P voice & video calls. Group calls up to 8. WebRTC direct — your ISP sees traffic, not content. CallKit on iOS.

class Stories

24-hour stories. P2P distributed — not stored on any server. Photo, video, text. React with emoji. Auto-delete guaranteed.

🎭 class AnimatedStickers

60 animated Lottie stickers in 3 packs. Create your own. Share packs P2P with friends. Smooth animations, tiny files.

📍 class LiveLocation

Share location: static or live (15min/1h/8h). OpenStreetMap — no Google tracking. Coordinates encrypted E2E. P2P only.

🤖 class BotPlatform

Bots are regular Hooly users with keypair. No server API — P2P encrypted like any chat. Hooly Bot SDK for developers.

📊 class PollsAndMore

Polls (anonymous/quiz), scheduled messages, message editing (<48h), reactions on everything. Telegram-level features, Signal-level security.

/* Works where others don't */

Governments block messengers by blocking their servers. Hooly has no servers to block.

hooly — censorship-check

$ hooly --censorship-check

 

[BLOCKED] Telegram    → servers blocked in Iran, China, Russia (partial)

[BLOCKED] WhatsApp    → blocked in China, Iran, parts of Africa

[BLOCKED] Signal      → blocked in China, Iran, Egypt, Cuba

[LIMITED] Session     → ISP blocks seed nodes → needs VPN

[LIMITED] Keet        → DHT nodes can be blocked

 

[RESISTANT] Hooly     → no servers to block

   ├── P2P direct (WebRTC)

   ├── Mesh networking (BLE + Wi-Fi Direct — NO internet needed)

   ├── Multi-hop relay (messages jump through nearby peers)

   ├── DTN (store-carry-forward, works days offline)

   ├── push via Apple/Google (they can't block their own infra)

   └── if all blocked → mesh works without ANY infrastructure

 

why_it_works:

  Blocking Telegram = block telegram.org servers easy

  Blocking Hooly = block ALL WebRTC traffic breaks video calls, gaming, streaming

                = block Apple/Google push breaks ALL apps on ALL phones

$ _

Traditional messengers rely on their own servers. Block those servers — the messenger is dead. That's how countries like China, Iran, and Russia restrict messaging apps.

Hooly has no servers to block. Messages travel directly between devices using WebRTC — the same technology powering video calls in your browser. Blocking WebRTC would break video conferencing, online gaming, and streaming for the entire country.

Push notifications use Apple and Google infrastructure. Blocking those would disable ALL app notifications for every iPhone and Android in the country — no government wants that.

The only way to block Hooly is to shut down the entire internet. And even then — Hooly's mesh network works WITHOUT internet. Messages travel through nearby devices via Bluetooth and Wi-Fi Direct. No servers, no internet, no way to block.

// Note: While Hooly's architecture is censorship-resistant by design, no tool can guarantee 100% access in all circumstances. Deep packet inspection (DPI) may detect WebRTC patterns. Using a VPN for the initial connection adds an extra layer.
hooly — status

$ hooly --status

status : ready_for_release

version : 1.0.0

tests : 939 passing (+ 35 bot SDK)

sprints : 14 complete

server_data: 0 bytes // as always

// ready for a messenger that respects you?

$ _