Komms Try Komms

Komms 0.4.2 · test Beta

A first conversation.
A useful beginning.

Bring two test devices and someone you trust. Start on the same local network, then explore what happens when the route changes.

01 / Get the app

Choose your test device.

This is an unsigned, pre-production test release. It has not had an independent security audit. Use disposable conversations; do not rely on it for emergencies, high-risk communication, or production work.

DESKTOP

Windows

Windows 10 / 11 · x64

Unsigned installer. SmartScreen may warn.

Download EXE
DESKTOP

macOS

Intel & Apple silicon

Unsigned, unnotarized DMG. Expect Gatekeeper warnings.

Download DMG
MOBILE

Android

Android 8.0+ · arm64

Google-free APK, signed with a test/debug certificate.

Download test APK
DEVELOPERS

iOS Simulator

Mac with Xcode required

Simulator only. There is no installable iPhone or iPad release.

View Simulator archive →
Before opening: verify your download

Download UNSIGNED-TEST-SHA256SUMS from the same release page. Compare your file’s SHA-256 with its exact filename in that manifest. A match checks file integrity; it is not a production signature or an independent security review.

Windows PowerShell: Get-FileHash -Algorithm SHA256 <file>
macOS: shasum -a 256 <file>
Linux: sha256sum <file>

If the digest differs, stop. Follow the full installation guide for package-specific details and migration precautions.

02 / Connect & send

Say something ordinary.

The aim is one verified, two-way conversation. These checkboxes are a temporary checklist for you; nothing is submitted or saved.

Start on the same trusted Wi-Fi or LAN, with both apps open. Guest-network isolation and local firewalls can prevent discovery. This Beta has no qualified public bootstrap or mailbox defaults, so a fresh install on two unrelated networks may need deliberate operator configuration. A Connect code does not create a network route.

0 of 6 steps checked. This is your checklist, not a qualification result.

Know what happened

Sent is a step.
Delivered is a receipt.

Komms keeps these states separate so you can see what the network has actually done.

Queued
The message is held locally, waiting for a suitable route.
Sent
The next hop has accepted custody. That may be an intermediary; it does not prove the recipient has it.
Delivered
An authenticated end-to-end receipt confirms delivery. It does not mean the person has read it.

If you get stuck

A few things worth checking.

The app says “Waiting for a route”

Keep both nodes running and check that the devices can reach one another on the local network. Guest Wi-Fi may isolate devices. If you are on separate networks, review the configured bootstrap, direct route, and mailbox settings in the self-hosting guide. Private mode currently needs a working local Tor setup. Switching modes alone does not create a route.

I added someone, but the message is still queued

A Connect code establishes contact information, not reachability. Check the receiving device’s Message Requests, keep both apps open, and inspect the connection settings. Do not treat a local peer count or a wake notification as proof that a message arrived.

Can I try radio or two different networks?

Yes, as a separate test with deliberately configured routes and suitable hardware. The physical radio and broader network qualification work remains open. Record the exact setup and result using the field testing guide; a successful local test does not prove those paths.

03 / Share what happened

“I got stuck here”
is useful feedback.

Tell us the version, devices, operating systems, broad network setup, steps, and expected versus actual result. Include timings when you can.

Remove message content, Connect codes, safety numbers, recovery material, tokens, identities, and private addresses. Report security issues privately.