Compare
Knit vs Bitchat
Two open-source mesh messengers that turn the crowd into the network — one runs on every phone, one goes deeper on Android.
Last reviewed: August 2026
Bitchat and Knit are the same species: open-source mesh messengers that turn a crowd of phones into the network — no servers, no accounts, no phone numbers. Bitchat arrived in 2025 with Jack Dorsey behind it and an IRC flavour: nicknames, slash commands, drop-in rooms. Knit plays the same game as a full messenger, on a mesh that uses Wi-Fi as well as Bluetooth.
The short version: in a mixed crowd of iPhones and Androids, Bitchat is the one everyone can install. If your people are on Android, Knit gives you the real messenger — photos, voice notes, encrypted groups, history, moderation — and the bigger radio.
| Feature | Knit | Bitchat |
|---|---|---|
| Works with no internet | Yes | Yes |
| Multi-hop mesh — messages relay phone to phone beyond your own radio | Yes | Yes |
| Meshes over Wi-Fi as well as Bluetooth1 | Yes | No |
| Store & forward for offline peers | Yes | Yes |
| Open room with everyone nearby2 | Yes | Yes |
| End-to-end encrypted direct messages | Yes | Yes |
| Named group chats, end-to-end encrypted | Yes | No |
| Forward secrecy3 | Yes | Live sessions only |
| Photos, GIFs, voice notes & reactions | Yes | Text only |
| Keeps your chat history, encrypted at rest | Yes | No, ephemeral by design |
| On-device AI moderation | Yes | No |
| Works over the internet4 | Yes, via optional relays | Yes, via Nostr relays |
| iPhone & Mac apps | No | Yes |
| Free, no ads, open source | Yes, GPLv3 | Yes, public domain |
- 1Wi-Fi Aware gives Knit's mesh the bandwidth for photos and GIFs, fetched on demand so large files never flood it; Bluetooth LE alone has little room for more than text.
- 2Both open rooms are plaintext by design — an open broadcast, like talking out loud in a crowd. In Knit, the sealed part is direct and group chats.
- 3Knit rotates keys per block of messages, not per message, and a chat with someone on an older Knit build falls back to the previous static-key scheme, which has none. Spent keys are deleted, so mesh traffic recorded today can't be decrypted later.
- 4Knit's Internet relays are opt-in and carry only conversations you already started nearby, as sealed frames the relay can't read — no accounts, no discovery, and you can run your own. The Nearby room stays radio-only.
Where Knit wins: a full messenger on a bigger mesh
Both apps relay messages hop by hop across whoever is around, but they aren't carrying the same things. Knit meshes over Wi-Fi Aware as well as Bluetooth LE, and that bandwidth is what makes it a complete messenger rather than a text channel: photos, GIFs and voice notes ride the mesh on demand — a file only crosses when someone taps it — alongside reactions, inline replies and @-mentions in a Signal-style app your friends already know how to use.
Knit also has real groups: named, members-only and end-to-end encrypted, the same as every direct and group chat in the app — sealed down to the mentions and image attachments, verifiable in person with a safety number or QR code. Bitchat's rooms run the other way: its local mesh chat and location channels are public spaces, with encryption reserved for one-to-one DMs.
And Knit expects to be lived in. Your chats are still there tomorrow, encrypted at rest under a hardware-backed key that stays out of cloud backups, and the open Nearby room ships with an on-device AI filter that screens abuse and blurs explicit images without an upload anywhere. If the app is going to hold your group thread for the weekend — the campsite, the crew, the block during an outage — that's the difference between a messenger and a walkie-talkie.
Where Bitchat wins: everyone can install it
Bitchat runs on iPhone, Android and Mac, and in a mixed crowd that decides it — the mesh you can actually raise is the one everyone's phone can join. Knit is Android-only today. Bitchat's location channels are their own trick, too: public rooms scoped to a place, riding Nostr relays when there's internet — something Knit has no answer to.
It forgets on purpose, too. Timelines live in memory, little is written down, and a triple tap wipes the lot. If you want a messenger that keeps nothing, that's a real feature — and the opposite of what Knit is built for.
Security, side by side
The two make the same basic split: private messages are encrypted, the open room is not. In Knit the sealed side is direct and group chats — end-to-end, down to mentions and image attachments — and the open side is the public Nearby room, an open broadcast, like talking out loud in a crowd. In Bitchat the Noise protocol seals one-to-one DMs, while the local mesh chat and geohash channels are public by design. Neither app pretends its open room is anything else.
Forward secrecy is where the details differ. Knit rotates keys as a conversation runs and deletes the spent ones — per block of messages, not per message, and a chat with someone on an older Knit build falls back to the old static-key scheme until they update. Bitchat's live Noise sessions are forward-secret, but by its own documentation the store-and-forward envelopes that wait for offline peers are sealed without it. Either way the promise is about recorded traffic: on Knit, messages are also encrypted at rest under a hardware-backed key, so reading them takes unlocking the device, not stealing it.
The browser demo shows the hop-by-hop idea without installing anything: knock out a cell tower, then walk a message across a crowd.
Choose Bitchat if…
- Your crowd is a mix of iPhones and Androids — Bitchat is the one everybody can install.
- You want place-scoped public rooms — geohash channels over Nostr — alongside the mesh.
- You want nothing kept: memory-only timelines and a panic wipe matter more to you than saved history.
Choose Knit if…
- Your people are on Android and you want a real messenger on the mesh: photos, GIFs, reactions and named encrypted groups.
- The crowd channel should stay readable — Knit's on-device AI filter handles abuse and explicit images without an upload.
- You want your chats still there tomorrow, encrypted at rest, instead of gone with the session.
- You want the bigger radio: Wi-Fi Aware meshing alongside Bluetooth LE.
Common questions
Can Knit and Bitchat talk to each other?
No. Different protocols, so a Knit phone and a Bitchat phone can't exchange messages even side by side — each app only meshes with itself. If your group is split across the two, pick one and standardise.
Which one is more private?
They make different promises. Both encrypt private messages end-to-end and both run their open rooms as plaintext broadcasts anyone in range can read — in Knit the sealed part is direct and group chats, in Bitchat it's one-to-one DMs. Knit adds forward secrecy with stated limits (keys rotate per block of messages, and a chat with someone on an older Knit build falls back to a static-key scheme without it) and keeps your history encrypted at rest, so reading it takes unlocking your phone. Bitchat's answer is to keep almost nothing on the phone at all: memory-only timelines and a panic wipe. Decide which of those matches your worry.
Why does Knit have photos when Bitchat is text-only?
Radio bandwidth, mostly. A Bluetooth LE mesh moves small packets reliably but slowly, which suits text. Knit meshes over Wi-Fi Aware as well, and moves images on demand — a photo crosses the mesh only when someone taps to fetch it — so bigger files ride without flooding the network.
Can I run both?
Yes — nothing about one interferes with the other. Some people will want exactly that: Bitchat as the room everyone can join from any phone, Knit as the messenger for the Android group that's actually organising things.
Which app should my festival group use?
Count the iPhones. If your group is mixed, Bitchat — being installable by everyone beats any feature on this page. If you're all on Android, Knit carries more: the named group for your crew, photos from the pit, and messages that wait in the mesh until your friends wander back into range.
We checked the Bitchat facts on this page against the Bitchat project's own README and whitepaper; the date above says when. Bitchat is an independent project, released into the public domain by its authors, and its GitHub repository has the latest. Spotted something wrong or out of date? Tell us and we’ll fix it.
← Back to home