VOIKATTO MESSENGER

END-TO-END ENCRYPTED • EPHEMERAL MESSAGING

Private, anonymous, and auditable messaging for privacy-conscious users. Connect via the main network node (main.voikatto.xyz), your own node, or route through Tor for extra anonymity.

User Repository Node Repository

Key Features

🔐

End-to-End Encryption

All messages are encrypted on the sender device and only decrypted on the recipient device. Keys never leave users' devices. Not even the node operators can read message contents.

🗑️

Ephemeral Server Storage

Messages are stored on the node only until both recipients confirm they have received them, then they are automatically purged from the server to reduce persistent traces.

🌐

Flexible Node Architecture

Connect to the official main node (main.voikatto.xyz), use your own hosted node, or combine with Tor for layered anonymity. Failover and federation-friendly design.

🧩

Self-Hosted Node

Developers and server operators can run their own node using the messenger-node repo. Nodes include built-in admin commands and fine-grained moderation controls.

🛡️

Privacy-First Policies

No analytics tied to user identity. Minimal logging for operational health only, and optional local-only histories. Default policies prioritize user anonymity.

⚡

Performance & Reliability

Lightweight desktop client optimized for speed. Secure transport, reconnect/resume, and efficient message routing to keep latency low.

How It Works

Key exchange & encryption: Each user generates a long-term identity keypair and per-conversation ephemeral keys. Messages are encrypted using proven primitives (e.g. X25519 + AES-GCM or equivalent), negotiated locally. Private keys are stored only on the device.

Delivery & deletion: Messages are delivered via the selected node. Nodes act as encrypted mailboxes: store ciphertext until recipients confirm receipt. Once both endpoints acknowledge delivery, nodes delete corresponding ciphertext.

Anonymity paths: Choose main.voikatto.xyz, your own node, or route traffic through Tor. Running a personal node removes reliance on public infrastructure and minimizes metadata exposure.

History & portability: Clients can optionally save a local encrypted history file for the user’s convenience. This history remains local and encrypted with the user's passphrase.

Developers & Node Operators

Node repository

Full server source, documentation and deployment examples:

github.com/voikatto/messenger-node
# Example built-in server commands (node CLI) start — start node daemon on configured port init — initialize node identity and keys join [addr] — connect to another node / bootstrap health — show node health and queue stats purge — force-purge a message or conversation backup — export encrypted local backup

User client repo

Desktop client source, build instructions and cross-platform packaging:

github.com/voikatto/messenger
Notes for contributors:
  • Security-first: PRs must include tests, threat model updates, and changelog entries.
  • Documentation: node and client both include README and deployment guides.
  • License: permissive license recommended for community hosting; see repo for details.

Get Started

Download or build the client from source, or deploy your own node. Repositories, docs and examples are linked below. For maximum anonymity, combine your node with a Tor gateway.

Download Client (zip) Download Node (zip)

Official main node: main.voikatto.xyz