DocumentationGetting started

Public beta coming soon. These docs describe Komms as it will work at launch. Features still on the way are marked Coming soon.

Updated 22 October 2026

What is Komms

One secure app for teams and communities. Chat, share files and make decisions, end-to-end encrypted, on a network no single company controls.

View as Markdown

Komms is a messaging app for teams and communities. It does the everyday jobs of a chat tool (channels, direct messages, replies, reactions and file sharing) with two big differences:

  • Private conversations are end-to-end encrypted. Only the people in a conversation can read it. Komms and the operators who run the network can't.
  • Your account and your history belong to you. Your identity lives on the Kaspa network, not in a Komms database, and you can export a copy of your history that anyone can check.

Two products, one app#

Komms Business Komms Community
For Companies and teams Clubs, projects and online communities
You create A workspace A server
Priced Per workspace, never per seat Per server, never per member
Typical use Private team channels, client channels, files Public and invite-only channels, members who come and go

Both use the same app and the same account. Read Komms Business or Komms Community? to pick the right one.

What makes it different#

  • Sign in with a passkey. No password to leak or phish. See Create your account.
  • Flat pricing. One price per workspace or server, with no per-seat fees and no member limits. See Plans and pricing.
  • A network, not a data centre. Messages are relayed and files stored by independent operators, who are paid through Bittensor subnet 27. Kaspa keeps the order of events. See How Komms works.
  • Proof you can keep. Every person's messages are anchored on Kaspa, so a conversation's history can be checked without trusting Komms. See Message delivery and anchoring.

Note

Komms is preparing for its public beta. These docs describe how Komms works at launch. Anything still on the way is marked Coming soon. For where things stand today, see Network status.

Where to go next#