Written for a few people, not everyone
Add a friend by their exact username, or share your Knock Code — a personal QR code — and start a conversation. There are no public profiles, no follower counts, no discovery feed.
A private messenger
Knock
A private messenger for your closest people.
One-to-one conversations, end-to-end encrypted. Knock is built for the few people you actually talk to — not a feed, not a network, not a following count.
Knock, the interaction
Tap Knock in a conversation and it lands on the other side at once — two bars, two people, one small sound.
End-to-end encrypted, by design
Messages, photos, videos, voice messages and files are encrypted on your device before they ever leave it, using the Signal Protocol (via libsignal) with post-quantum key exchange. Knock's server stores and delivers ciphertext — it cannot read what you send.
React, reply, edit — still encrypted
Reactions, replies, edits and deletions travel the same encrypted way as your messages. Knock's server doesn't see which message you reacted to, what you said, or what you changed.
Presence, on your terms
Show when you're around, or don't — it's a setting, and it only ever works both ways: if you don't share your presence, you don't see anyone else's either. Read receipts can be turned off the same way.
What Knock can and can't see
Knock's server never sees the content of your messages, photos, videos, voice messages or files — only ciphertext it cannot read. To connect and deliver them, it does process some information: who you talk to, when, and basic account details like your username. The Security page explains exactly what that means, in plain terms.
Knock is currently in private alpha. It hasn't had an independent security review yet, and some planned protections — like verifying a friend's identity — don't have an interface yet. Details on the Security page.