Cinny

Ajay Bura launched Cinny in 2021 as a web client for the Matrix protocol to give users an organized, familiar chat interface without the visual clutter of existing decentralized tools. By packaging Matrix into a static single-page application that connects to any standard homeserver, it allows organizations to run real-time messaging on their own infrastructure. That origin gives small teams and technical leads a Discord-like communication layer with complete custody over data, keys, and message archives.

Why Cinny instead of Discord

Discord operates as a centralized commercial silo where user communications, attachments, and identity records reside on corporate servers. For agencies and operations teams managing proprietary client assets or private infrastructure communications, hosting discussions on a third-party platform introduces regulatory exposure and vendor lock-in. Cinny replaces that dependency by functioning as a client for the open Matrix federation protocol. When paired with a self-hosted homeserver such as Synapse or Conduit, databases and cryptographic credentials stay under internal control, protected by Matrix's Olm and Megolm end-to-end encryption standards.

The operational trade-off centers on platform breadth versus governance. Discord provides zero-configuration setup, ubiquitous mobile apps, and low-latency voice channels with screen sharing. Cinny focuses on structured text communication, spaces, and direct messaging, handling audio and video through basic WebRTC calls. While running Cinny requires selecting or managing a Matrix homeserver, teams eliminate third-party tracking, prevent unexpected account suspensions, and protect confidential discussions from commercial data harvesting.

What it does well

• Static distribution: Compiles into static web assets that serve from any HTTP server or reverse proxy without a Node.js runtime daemon.
• Matrix Spaces hierarchy: Organizes rooms and direct chats into spaces, letting agencies isolate client channels cleanly within one interface.
• End-to-end encryption: Handles cross-signing verification, key backups, and emoji verification to keep messages confidential across distributed teams.
• Intuitive interface: Arranges spaces, rooms, and chat panes into a layout that non-technical staff can navigate without training.
• Fleet configuration: Pre-configures default homeservers and room directories via config.json, letting administrators lock connection endpoints for team members.