Keet

Every mainstream messenger asks for trust. The company promises not to read messages or sell metadata, and users accept that on faith because the messages pass through its servers either way. Keet, from Holepunch Inc., takes the servers out. Messages, files and calls travel directly between devices with end-to-end encryption. Holepunch says it cannot read chats, does not collect metadata and does not store messages or personal data. The privacy argument shifts from trust in a company to the absence of one.

That shift shapes everything else. There is no sign-up with a phone number or email. Identity is a 24-word seed phrase, a convention borrowed from cryptocurrency wallets, and the same phrase restores chats and contacts on a new device. Additional devices join by scanning a QR code or opening a sync link from a device that is already connected. Beyond that, the feature list reads like a full-service messenger: one-to-one and group chats, HD audio and video calls designed for large groups, file transfers with no size cap, community Rooms, and Broadcast Rooms for one-to-many publishing.

The business model is as unusual as the plumbing. Keet carries no ads and no subscriptions, and it is free on iOS and Android. On the iOS App Store it holds a 4.6 out of 5 average from 309 ratings. That is a good rating from a modest sample. The rating points to a core audience that has bought into the model. The feature gaps and onboarding friction explain why it has not crossed into the mainstream. The profile is early adopters who accept rough edges. It fits a product still earning its place beyond the privacy-conscious niche.

• Peer-to-peer, end-to-end encrypted transport: Messages, files and calls move directly between devices instead of through company servers. Holepunch says it cannot read chats, collects no metadata and stores no messages or personal data.
• Seed-phrase identity: No phone number and no email. A 24-word seed phrase is the account, and it restores chats and contacts on another device.
• QR and link device sync: New devices are added by scanning a QR code or using a sync link from a device that is already connected.
• Chats and HD calls: One-to-one and group messaging, plus HD audio and video calls that Holepunch says are built to stay smooth in large groups.
• Unlimited file transfers: Files go directly between peers, so there is no size limit.
• Rooms and Broadcast Rooms: Rooms host group conversations. Broadcast Rooms let creators post to an audience that can respond only with reactions.
• No ads, no subscriptions: Free on iOS and Android.

The Architecture Is the Product

Most privacy messengers compete on encryption and policy. Keet competes on topology. A central server is where metadata normally piles up: who talks to whom, when, and how often. Removing that server is a stronger guarantee than any retention policy, because data that never reaches a company cannot be breached, subpoenaed or monetized from it. For journalists, activists, legal teams and anyone handling sensitive material, that distinction is the whole sales pitch.

The trade-off is structural too. A server also acts as a mailbox, a relay and a fallback. Without one, the system has to handle reachability and multi-device consistency some other way. Holepunch’s answers are direct transfer, seed-based restoration and QR pairing, and they are coherent. Still, a peer-to-peer design asks the devices themselves to do work a data center would otherwise absorb. That is a sensible price for the target audience. It is a harder sell to someone who wants a messenger to behave like a utility they never have to think about.

Identity Without an Account

The 24-word seed phrase is Keet’s most consequential design decision and its biggest source of friction. It solves real problems. No phone number means no carrier-linked identifier tying the account to a real-world identity. No email means no password-reset route for an attacker to exploit. The phrase is portable, self-custodied and works across iOS and Android.

Self-custody cuts both ways, though. With no email or phone number on file, there is no obvious recovery route if the phrase is lost, because the phrase is the account. Crypto users have learned that discipline. Most messaging users have not. This is where onboarding matters most. A product that hands newcomers a 24-word secret needs to explain early and patiently what the phrase is, why it matters and where to keep it. The thin onboarding suggests Keet still assumes a familiarity its broader audience will not have.

Device sync is the right counterpart. QR pairing relies on physical proximity, which is intuitive, and the sync link offers an alternative when scanning is not practical. Requiring a device that is already connected keeps the trust chain intact. No new device appears without an existing one vouching for it.

Rooms, Broadcasts and the Shape of Conversation

Keet’s social layer is broader than its privacy-tool reputation implies. Rooms handle group conversation. Broadcast Rooms add a one-to-many channel where the audience can react but not reply. That restriction is a sensible moderation choice. Creators get reach without a comment section to police, and audiences get a feed without the noise. The format suits announcements, community updates and creator newsletters, and it brings them inside an encrypted, serverless envelope.

The product’s room-first bent hints at a messenger that grew toward conventional chat. The core messaging now covers the basics. Expiring messages would suit a serverless design naturally, and their absence is a gap Holepunch should close.

Calls and Files Without a Middleman

Holepunch pitches HD audio and video calls built to stay smooth in large groups. Group video is a heavy workload for a peer-to-peer system. The claim is ambitious, and it is Holepunch’s to prove.

The no-limit file transfer is a clear benefit of the architecture. Server-based services cap file sizes because they pay to store and relay those files. Keet does neither, so it has no reason to cap them. The practical ceiling moves to the users’ own connections. A direct transfer depends on both ends, so whether a multi-gigabyte file goes over mobile data becomes a question of data plans and patience rather than policy.

The Business Model

There are no ads and no subscriptions, so the app contains no visible revenue stream. Users are not the product, and nothing in the app is paywalled. For individuals that is a clear benefit. Teams considering moving their daily communication onto Keet should treat the long-term funding picture as an open question worth asking Holepunch about.

Keet’s interface carries an unusually heavy explanatory burden. It has to surface concepts that mainstream messengers hide or never need: a seed phrase, device pairing by QR code or sync link, and three distinct conversation modes in direct chats, Rooms and Broadcast Rooms. It has to do all that while still feeling like a chat app. The thin onboarding suggests the UI currently handles chatting better than explaining. When security depends on users understanding their own key, that is a design flaw, not a cosmetic one.

On performance, the architecture sets expectations. Cutting out the server hop can reduce one kind of overhead, but a phone that sends files and carries calls directly does more of its own networking than one that hands everything to a server. Battery and data use are therefore reasonable things to watch, as a design-level consideration rather than a documented problem. Stability is the clearer concern. A peer-to-peer app carries more reliability risk than a mature server-backed messenger. That is tolerable for an enthusiast tool. It is a real risk for a team that depends on the app every day.

On iOS and Android, Keet is a touch-first app with identical economics: free, with no ads and no subscriptions on either store. The feature set is the same on both mobile platforms. QR pairing makes good use of the phone’s camera, and the sync link covers devices where scanning is awkward.

Identity lives in the seed phrase rather than a store account or phone number. That means switching between iOS and Android should not strand a user’s history, since the phrase restores chats and contacts on another device. This portability is a meaningful advantage over backups tied to one platform.

Both mobile operating systems limit what apps can do in the background. A peer-to-peer messenger leans on direct connections far more than a server-backed one. As a result, behavior when the app is not in the foreground is where a phone build of a P2P messenger has the most to prove. The App Store rating of 4.6 out of 5 from 309 ratings points to a satisfied core audience, though the sample is modest.

Keet makes a practical privacy argument. Instead of promising to handle data responsibly, it removes the place where data would accumulate. Holepunch backs that with a feature set that reaches past a niche tool: group calls, uncapped file transfers, Rooms, and a reaction-only broadcast format. The price is zero, with no ads or subscriptions attached. The App Store rating of 4.6 out of 5 from 309 ratings reflects an audience that understands what it is getting.

What holds Keet back is everything around the architecture. A 24-word seed phrase is a serious responsibility to hand a messaging user, and the thin onboarding leaves too much of the explaining to the user. Reliability questions and missing comforts like expiring messages keep it short of a universal recommendation. We recommend Keet to privacy-conscious users and small teams prepared to manage their own keys. For the broader public, it is a messenger to watch as it matures.