Matrix / Synapse
The core of the business messenger: room management, event exchange and client interaction.
IN-HOUSE PROJECT / VESS.SU
Business messenger
powered by Matrix and Element.
We deployed VESS.SU for our own needs and demonstrations for companies. The running system shows how to organize business communication with encrypted rooms and the option of hosting on an organization's server.

ElementPROJECT GOAL
Build our own Matrix communication environment and use it to demonstrate the solution to other companies. Show the client, rooms and server architecture on a running system.
VESS.SU is ITDALEX's own project. It lets us discuss communication workflows and deployment requirements with a customer before installing a separate server in their organization.
HOW IT WORKS
Simplified deployed stack.
No addresses, keys or access credentials.
The server can be hosted within an organization's infrastructure. Hosting, network access and interaction with external Matrix servers are chosen to meet its requirements.
PROJECT TECHNOLOGIES
The services behind
VESS.SU infrastructure.
The core of the business messenger: room management, event exchange and client interaction.
The user interface for communication in the Matrix ecosystem.
A dedicated component for sign-in and managing user sessions.
Server-side data storage within the deployed infrastructure.
Media server and authorization service for MatrixRTC calls.
Deployed tools for managing the Matrix server.
Components run in separate containers. Backups, updates and availability monitoring require a separate operations procedure.
SECURE COMMUNICATION
In rooms with end-to-end encryption enabled, clients encrypt message content. The server relays encrypted events and cannot obtain their plaintext merely by acting as the server.
Metadata, accounts and some service information remain accessible on the server side. Device security, session verification and recovery key protection also affect message security.
E2EE applies to encrypted rooms, not automatically to all service data. Self-hosting does not prevent copies on other servers when federated rooms are used. About Matrix encryption ↗
INTERFACE AND BRANDING
Branded sign-in screen,
clients for desktop and smartphone.

Logo, colors and sign-in design, shown with VESS.SU. We agree your organization's branding to match its visual identity.

Element interface example: users, rooms, messages and call buttons. Names, avatars, chat titles and conversation history are blurred.
Anonymized copy. Click the image to inspect the interface.
Mobile interface example: chats, search and navigation. Contacts, room names, dates and message previews are blurred.
Anonymized copy. Click to enlarge.Explore the client, direct conversations and team rooms.
An explanation of E2EE, device verification and recovery keys.
Discuss hosting, user management and ongoing support.
VESS.SU includes deployed LiveKit and JWT components. Calling demonstrations are arranged separately.
OUTCOME
VESS.SU is deployed as our own Matrix project and a demonstration platform for companies. The server environment includes a client, authentication, database, administration and calling components.
Customer deployments separately define room structure, user provisioning, encryption policy and maintenance procedures.
LET'S DISCUSS BUSINESS MESSAGING