This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
PrivaMesh
Private messaging with no servers or phone number
PrivaMesh is a serverless, end-to-end encrypted iPhone messenger with no account database, phone number, email, ads, trackers, or analytics. Identity and messaging keys live in the iOS Keychain; contacts and history stay on-device. X3DH, Double Ratchet, fresh per-message keys, fixed-size padding, one-time addresses, and cover traffic protect conversations while a public, decentralized transport carries only ciphertext.
I built PrivaMesh around a simple question: if end-to-end encryption protects message content, why should a central service still know that an account exists, who it talks to, and when?
PrivaMesh is a serverless private messenger for iPhone. It has no account database, phone-number signup, email requirement, ads, trackers, or analytics. Identity and messaging keys live in the iOS Keychain, while contacts and chat history stay on the device.
Under the hood:
• X3DH establishes the first shared secret
• Double Ratchet creates a fresh key for every message
• Opt-in cover traffic makes timing analysis harder
• A public, decentralized transport carries ciphertext; no PrivaMesh account server stores it
The app is open source and free to download, with optional in-app purchases for higher usage limits.
This is a different set of tradeoffs from a traditional messenger. I’d especially value feedback on the privacy model, onboarding, and everyday chat experience. What would you want to verify or improve before trusting a serverless messenger?
About PrivaMesh on Product Hunt
“Private messaging with no servers or phone number”
PrivaMesh was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #84 on the daily leaderboard. PrivaMesh is a serverless, end-to-end encrypted iPhone messenger with no account database, phone number, email, ads, trackers, or analytics. Identity and messaging keys live in the iOS Keychain; contacts and history stay on-device. X3DH, Double Ratchet, fresh per-message keys, fixed-size padding, one-time addresses, and cover traffic protect conversations while a public, decentralized transport carries only ciphertext.
On the analytics side, PrivaMesh competes within Messaging, Open Source, Privacy and GitHub — topics that collectively have 173.3k followers on Product Hunt. The dashboard above tracks how PrivaMesh performed against the three products that launched closest to it on the same day.
Who hunted PrivaMesh?
PrivaMesh was hunted by makom. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of PrivaMesh including community comment highlights and product details, visit the product overview.
makom
Hey Product Hunt 👋
I built PrivaMesh around a simple question: if end-to-end encryption protects message content, why should a central service still know that an account exists, who it talks to, and when?
PrivaMesh is a serverless private messenger for iPhone. It has no account database, phone-number signup, email requirement, ads, trackers, or analytics. Identity and messaging keys live in the iOS Keychain, while contacts and chat history stay on the device.
Under the hood:
• X3DH establishes the first shared secret
• Double Ratchet creates a fresh key for every message
• Fixed-size padding reduces message-length leakage
• One-time addresses reduce linkability
• Opt-in cover traffic makes timing analysis harder
• A public, decentralized transport carries ciphertext; no PrivaMesh account server stores it
The app is open source and free to download, with optional in-app purchases for higher usage limits.
This is a different set of tradeoffs from a traditional messenger. I’d especially value feedback on the privacy model, onboarding, and everyday chat experience. What would you want to verify or improve before trusting a serverless messenger?