# Roadmap

What ships at launch, what follows in the weeks after, and the longer path from messaging to AI coordination and proving.

Komms launches as a public beta. Work is split into what ships at launch, what follows inside the launch window, and what comes after.

## At launch

- Messaging for teams and communities, on the web and as desktop apps for macOS and Windows
- Instant delivery with anchoring on Kaspa
- Accounts you control, with passkeys and a recovery kit
- Verifiable history and full export
- Plans billed on the web, with storage allowances
- Independent miners and a second, independently run validator on the Komms subnet

## In the launch window {{soon}}

- iOS and Android apps with push notifications
- Voice and video calls, end-to-end encrypted
- File transfers with expiring links
- Paying in KAS
- Search across your full local history
- A web portal for miners

## After launch

- Enterprise features, such as single sign-on and compliance export
- **Komms Publish**: build your own app on the Komms network
- **Komms RPC**: paid access to Kaspa nodes run by Komms miners

## The longer view

The four phases from the [Komms Roadmap (PDF)](files/komms-roadmap.pdf):

1. **Open communication protocol.** The flagship Komms app, and a shared backend other apps can build on.
2. **Decentralised Kaspa RPC.** Every Komms miner already runs a Kaspa node; that capacity becomes a scored service for developers, wallets and AI agents.
3. **AI-to-AI communication.** Agents that confirm each other's identity, talk privately, record the outcome on Kaspa and settle payments.
4. **Validation and zero-knowledge proving.** Komms miners grow into an independent proving layer anchored to Kaspa.

Later phases depend on the earlier ones working in public first. Dates are announced when each is ready, not before.