Skip to content
enclessa

Core · every plan

Messaging that keeps its shape as you grow

Enclessa messaging organises work into teams, categories and channels, with threaded replies, reactions, full Markdown and message search. Direct messages and group direct messages are end-to-end encrypted with MLS, while channels are readable by the server so that search, retention and compliance export can work on them. Which mode a room uses is fixed when the room is created and shown in the room itself, so nobody has to guess.

At a glance

Structure
Teams → categories → channels → threads
Direct messages
End-to-end encrypted, no administrator override
Search
PostgreSQL full-text over channels and file contents
Formatting
Full Markdown, code blocks, tables, LaTeX
Permissions
Bitmask checked in the data layer, not the interface

How is a Enclessa workspace organised?

A team is the top-level unit and holds its own categories, channels and roles. Channels can be public to the team or private to the people invited into them, and one level of sub-channel keeps a busy category readable without turning the sidebar into a filing cabinet.

  • Public channels, private channels, direct messages and group direct messages
  • Categories with an emoji, ordering and permissions of their own
  • Read-only channels and admin-enforced categories fall out of the permission model
  • Favourites, mute, unread-only view and channel bookmarks in the sidebar

What can a message do?

Everything a working conversation needs and little that it does not. Threads collapse under the message that started them and have an inbox of their own, so a busy channel stays a channel rather than a list of tangents.

  • Threads, reactions, pins, saves, permalinks and mark-as-unread
  • Edit and delete inside windows the organisation configures
  • Mentions for a person, a role, a custom group, @here, @channel and @everyone
  • Scheduled messages, reminders and voice messages
  • Link previews generated behind SSRF protection, never by fetching from your browser

How does search work when some rooms are encrypted?

The capability moves rather than disappearing. In channels the server can read the message, so the server indexes it: PostgreSQL full-text search covers message bodies and text extracted from uploaded files. In end-to-end encrypted rooms the server holds ciphertext and cannot index anything, so the same search runs on your own device against a local encrypted index.

  • Server-side full-text search across channels and file contents
  • File search over names and extracted document text
  • Client-side search for encrypted rooms, against a local index

What about files and attachments?

Uploads are scanned for malware before anybody can open them, images get thumbnails, and video and document uploads have their metadata and text extracted for search. Every file carries the organisation it belongs to, which is what makes an export or a deletion complete rather than approximate.

  • Drag-and-drop upload with image thumbnails and document previews
  • ClamAV scanning and media extraction in a dedicated worker
  • Attachments in encrypted rooms are encrypted with the message

What this does not do

  • Group channels are server-readable by design — that is what makes search and compliance export possible. End-to-end encryption covers direct messages and group direct messages.
  • There is no document co-authoring, wiki or spreadsheet. Files are stored, versioned and displayed, not edited.
  • A room cannot be switched between encrypted and managed after it is created, because either the old history would be exposed or it would become permanently unreadable.

Related

Questions

Messaging: common questions

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

No card required to create a workspace.

PostgreSQLLiveKitNATS.ioPrometheusGitHubDocker