We built ChatMat because true connection requires mutual consent.
For years, we watched social platforms prioritize noise over intent. We saw users overwhelmed by unsolicited messages and fragmented group chats. ChatMat was engineered to restore order. By requiring a unique 4-digit code and explicit acceptance from every participant, we ensure that your digital space remains private, structured, and entirely under your control.
We refuse to compromise on three pillars: intentionality of access, transparency of status, and the user's right to gate their own communication. Every chat request is a deliberate choice. Every group member must validate their presence. Reliability is not a feature — it is the foundation of our protocol, ensuring that when you connect, it is because you both chose to.
SYSTEM ARCHITECTS
The engineers securing your connections.
Marcus Thorne
VP INFRASTRUCTURE
Previously: SRE at Cloudflare. BS Computer Engineering, Waterloo. Expert in zero-trust network design.
Jonas Vane
HEAD OF PLATFORM
Previously: Kubernetes core at Red Hat. MS Distributed Computing, CMU. Built multi-tenant orchestration.
Lena Kalu
DIRECTOR · RESEARCH
Previously: Research scientist at DeepMind. PhD Machine Learning, Oxford. Focus on privacy-preserving chat.
Hiroshi Sato
DIRECTOR · SRE
Previously: SRE at Netflix. BS Software Engineering, Waterloo. Owner of incident response playbooks.
- 01
Identity Assignment
User registers a unique handle and receives a secure 4-digit access code.
SECURE - 02
Code Distribution
Share your unique 4-digit code with trusted contacts to initiate connection.
READY - 03
Request Initiation
Counterparty enters your code to signal a desire to communicate.
PENDING - 04
Mutual Acceptance
Both parties must explicitly authorize the request to establish a secure tunnel.
VERIFIED - 05
Tunnel Encryption
Private communication channel is established between verified nodes.
ACTIVE - 06
Group Synchronization
In group settings, every participant must accept the invite to join the stream.
SYNCED - 07
Secure Messaging
Exchange data within the hardened, code-based environment.
LIVE - 08
Session Termination
Connections remain private and can be revoked at any time by either party.
CLOSED