# Enclessa

> Enclessa is in open beta: end-to-end encrypted messaging, video calls, task boards, time tracking and people management, hosted in the European Union.

Enclessa is a European collaboration platform in open beta, delivered as a hosted service at your-team.enclessa.app. It combines team messaging with channels and threads, end-to-end encrypted direct messages using MLS per RFC 9420, video calls with screen sharing, and twelve optional modules — task boards, GitHub sync, projects, customers, contracts, bookings, employee cards, mail, time tracking, personnel records, a Lexware Office ledger connector and an assistant — all on one permission model. There is a free plan, the infrastructure is run for you in the European Union, and every organisation can export everything it holds at any time. The open beta is open to anybody: no invitation, no waiting list, and no availability figure committed while it lasts.

## Release stage

Enclessa is in open beta: anybody can create a workspace today, without an invitation and without a waiting list. The platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta.

## Key facts

- Release stage: Open beta. Open to anybody; no invitation, no waiting list.
- Delivery: hosted service; each organisation is reached at your-team.enclessa.app
- Hosting region: European Union, one region. No per-country residency choice.
- Seller: established in Germany. EU VAT applies.
- Licensing: Enclessa is a commercial software-as-a-service product. It is NOT open source, the source is not published, and there is no licence to install or self-host it.
- Enterprise: a dedicated deployment of the same hosted service — separate database, storage and media nodes, in a region the customer names — operated and updated by Enclessa. It is not a self-hosted licence and there is no air-gapped option.
- Open source in the stack: every runtime dependency is open source, enforced by a licence gate in continuous integration. That is a claim about the components, not about Enclessa itself.
- Encryption: MLS per RFC 9420 via OpenMLS, for direct and group direct messages.
- Clients: web today; a macOS desktop app is in development; no mobile apps yet.
- Free plan: yes, permanent, up to 10 members, no payment card.
- Trial of a paid plan: 14 days, no payment card required.

## Features

URL: https://enclessa.app/features

### Messaging (core, every plan)
URL: https://enclessa.app/features/messaging

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.

Limits:
- 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.

### Encryption (core, every plan)
URL: https://enclessa.app/features/encryption

Enclessa encrypts direct messages end to end using MLS, the Messaging Layer Security protocol standardised as RFC 9420, implemented with the audited OpenMLS library. Each device holds its own key, the group re-keys as members and devices come and go, and the server operates only the delivery service — it never holds a key that could decrypt a message. That gives forward secrecy, so a key compromised today cannot open yesterday, and post-compromise security, so the group heals once the compromised device is removed.

Limits:
- Encryption covers direct messages and group direct messages. Managed channels are server-readable so that search, retention and compliance export can work.
- Meeting recording and telephone dial-in are not offered in end-to-end encrypted calls, because either would require decrypting the media somewhere you cannot see.
- Post-quantum key exchange and federation are kept architecturally open but are not implemented.

### Video calls (core, every plan)
URL: https://enclessa.app/features/calls

Enclessa video calls run on LiveKit and start from the channel or direct message you are already in, so nobody schedules a meeting to ask a question. Calls carry screen sharing, in-call chat, reactions, raise hand, a lobby and host controls, and a Calls surface lists what is live and what is ringing across your workspace. In end-to-end encrypted rooms the media is encrypted end to end as well.

Limits:
- Fifty participants per media node is the architectural target the system is built and instrumented for, not a figure measured with fifty real people in a room.
- Recording exists as a job that the media egress accepts; producing and delivering a finished recording file is not complete.
- Telephone dial-in, live captions, breakout rooms and transcription are planned and not built.

### Task boards (optional module)
URL: https://enclessa.app/features/boards

Enclessa task boards are kanban boards that belong to a team and inherit that team’s roles, so nobody administers a second permission model beside the first. A card links back to the channel and message the work came out of, which is the part a separate project tool cannot do. Boards are a module: they are off until an operator switches them on for the organisation.

Limits:
- Boards are off until an operator enables the module for the organisation.
- Dependencies, sub-items, automation rules, cross-board views and reporting charts are deliberately absent and will stay absent.
- The GitHub connector requires the boards module, because its cards are board cards.

### Time tracking (optional module)
URL: https://enclessa.app/features/time

Enclessa Time records two different things and refuses to confuse them: presence, meaning when somebody was at work, and project time, meaning what the work was for. A schedule sets each day’s target and the difference accrues in an overtime ledger rather than evaporating. Periods are submitted, approved and then locked, absence draws on an entitlement ledger, and every timestamp comes from the server rather than from a device clock somebody can change.

Limits:
- Time is off until an operator enables the module for the organisation.
- There is no shift planning or rota: the planner shows absence and does not schedule staff.
- Carry-over and expiry of entitlement and of overtime, and submission reminders, are designed and not yet built. The daily cap is applied to the balance; weekly limits, breaks, rest periods, night and Sunday work are flagged on the day rather than enforced.
- There is no productivity scoring and no ranking of people by output. That is a deliberate refusal.
- Introducing time recording is the employer’s decision and the employer’s responsibility. Where a works council exists, a system that records working time is generally subject to its co-determination under § 87 (1) no. 6 BetrVG, and a works agreement (Betriebsvereinbarung) may be needed before it goes live. Enclessa is the tool; it does not make that assessment for you.

### People (optional module)
URL: https://enclessa.app/features/people

Enclessa People holds employee records — including for people who never sign in — alongside an organisational structure of units, positions, locations and cost centres. Employment, position and reporting line are stored as effective-dated periods rather than as columns that get overwritten, so the answer to "who reported to whom last March" is a lookup rather than an argument. Onboarding and offboarding are workflows that actually reach into accounts, teams, boards and time tracking instead of producing a checklist somebody has to execute by hand.

Limits:
- People is off until an operator enables the module for the organisation.
- There is no payroll. Enclessa holds the records payroll needs and does not calculate or pay anybody.
- There is no recruiting or applicant tracking, no performance review cycle and no learning management. None of these are in scope.
- Introducing a personnel system is the employer’s decision and the employer’s responsibility. Where a works council exists, software that can be used to monitor employees’ conduct or performance is generally subject to its co-determination under § 87 (1) no. 6 BetrVG, and a works agreement (Betriebsvereinbarung) may be needed before it goes live. Enclessa is the tool; it does not make that assessment for you.

### Projects (optional module)
URL: https://enclessa.app/features/projects

Enclessa Projects is the module that records what an organisation is working on: a project with an owner, a customer, dates, a budget and the people on it, plus milestones, status updates carrying a health word somebody put their name to, and a log of the risks being carried and the decisions taken. It needs no other module — the smallest useful installation is a list of what the organisation is working on and who owns each one — and it lights up further panels when Boards, Time or Customers are installed beside it.

Limits:
- Projects are off until an operator enables the module for the organisation.
- There is no dependency graph, no critical path and no resource levelling — a project is a record of what is being done and by whom, not a scheduling engine.
- The day strip on the week board was planned with the agenda work and was not built.

### Customers (optional module)
URL: https://enclessa.app/features/customers

Enclessa Customers is the module that holds the companies an organisation works with: a record per company with an owner, a status and the words the organisation itself uses, plus contacts, addresses, a log of what was said and the date somebody will come back to it. Opening one customer shows the projects being run for them, the hours those cost and the appointments they booked, assembled from whichever modules are installed — and the financial fields are absent rather than blank when nobody present may see them.

Limits:
- Customers is off until an operator enables the module for the organisation.
- A contact is a record, not a login. There is no customer portal and no way for somebody outside the organisation to sign in and see their own record.
- It is not a sales pipeline: there are no deals, stages, forecasts or quotas.

### Contracts (optional module)
URL: https://enclessa.app/features/contracts

Enclessa Contracts is the module that produces the document an organisation sends a customer: what is being agreed, what recurs, what it includes, what exceeding it costs and what the total is. A contract is filled from the customer record rather than from a form, built out of typed blocks over a clause library so a shared paragraph is written once and referenced, checked by a readiness report before it may leave, and issued as a deterministic PDF signed with the organisation’s own certificate and frozen against further change.

Limits:
- Contracts is off until an operator enables the module, and requires the Customers module.
- Annex upload, a consumption statement against the hours Time recorded, and .docx import are deferred: the block type exists for the first, the route does not.
- There is no signing ceremony for the counterparty and no qualified electronic signature. What the module produces is a PDF the organisation has sealed, not a two-sided signing flow.

### Bookings (optional module)
URL: https://enclessa.app/features/bookings

Enclessa Bookings is the module that lets somebody outside the organisation ask for a time — an initial consultation, a viewing, a call — and somebody inside answer. Appointment types carry their own opening hours, duration and buffers; requests either arrive for approval or confirm themselves; and the visitor gets a link they can use to see or call off their own appointment without ever having an account. It is the one surface on the platform that answers without a session.

Limits:
- Bookings is off until an operator enables the module for the organisation.
- It books time with the organisation, not resources: there are no rooms, no equipment and no seat maps.
- There is no payment step. Nothing takes a deposit or a card at the point of booking.

### Cards (optional module)
URL: https://enclessa.app/features/cards

Enclessa Cards is the module that gives every employee a card derived from the employment in force on the date being asked about: a front they fill in themselves and can send to somebody who saves the contact without signing in to anything, and a back carrying their standing behind five visibility bands. Each card carries a per-organisation signature, so somebody at a reception desk can check that this person works here and in what position — and on the day the employment ends, the same check says so, without anybody having revoked anything.

Limits:
- Cards is off until an operator enables the module, and requires the People module.
- Wallet passes, the email-signature generator and batch printing were deferred and are not available.
- A card is not an access credential by itself. Entitlements are declared and exported; the system that opens the door is somebody else’s.

### Mail (optional module)
URL: https://enclessa.app/features/mail

Enclessa Mail is the module that reads and answers the organisation’s own mailboxes from inside the product: as many as it has, personal or shared, with access granted per mailbox to a person, a team or a role and to nobody else. It reads, answers, files and searches with the mail server kept as the truth rather than copied into a second one, sends under a granted identity through the organisation’s own relay, and appends the legal footer written once for the organisation.

Limits:
- Mail is off until an operator enables the module for the organisation.
- Enclessa does not host mail. It connects to mailboxes the organisation already has, and creating or deleting a mailbox happens in the hoster’s own console.
- Mail is not end-to-end encrypted. It is ordinary mail on your own server — the encryption guarantees on this site are about rooms in Enclessa, not about SMTP.

### Finanzen (optional module)
URL: https://enclessa.app/features/finance

Enclessa Finanzen is the module that turns recorded work into invoice drafts in the organisation’s own ledger. It pushes customers to Lexware Office and mirrors every invoice, credit note and reminder back with its PDF; it proposes an invoice from booked hours, grouped and rounded as agreed, and posts it there as a draft; and it marks those hours invoiced with the number the ledger gave them, so the same hour cannot be billed twice. It numbers nothing, sends nothing and finalises nothing — the ledger is the authority and this is the copy.

Limits:
- Finanzen is off until an operator enables the module, and requires the Customers module.
- The only ledger it connects to is Lexware Office. There is no generic accounting connector and no DATEV export from this module.
- It numbers nothing, sends nothing and finalises nothing. Anything that has to be legally final happens in the ledger.

### Companion (optional module)
URL: https://enclessa.app/features/companion

The Enclessa Companion is a module where somebody asks for something in their own words and gets either a fact read out of their own organisation or a change they are about to make to it. It finds only what the person asking is already allowed to see, it proposes rather than acts, every change it does apply can be taken back, and each tool it has carries a setting: off, propose and wait, or apply without asking.

Limits:
- The Companion is off until an operator enables the module for the organisation.
- It cannot read what you cannot. It has no privileged view of the organisation and no access to end-to-end encrypted rooms, which the server cannot read either.
- It was verified against a database and a scripted model rather than in a browser, and the module is new.

## Integrations

URL: https://enclessa.app/integrations

- [GitHub](https://enclessa.app/integrations/github) — Issues and pull requests become board cards and stay in step, with check results on the card and write-back you switch on deliberately.
- [Incoming webhooks](https://enclessa.app/integrations/webhooks) — A URL and a secret that let any system post into a channel, with a Slack-shaped payload and a bot account behind it.
- [Slash commands](https://enclessa.app/integrations/slash-commands) — Built-in commands for the things people do constantly, plus custom commands that call an HTTP endpoint you control.
- [Bot accounts](https://enclessa.app/integrations/bots) — Real accounts with real memberships, authenticated by a scoped token, unable to reach the console or mint another token.
- [The API](https://enclessa.app/integrations/api) — A generated OpenAPI surface, scoped access tokens with a closed vocabulary, and a CI job that fails the build if the document drifts from the code.

There is no marketplace, no third-party app directory, no single sign-on, no SCIM, and no connector for Slack, Jira, Linear, Asana, Notion or Zapier.

## Pricing

URL: https://enclessa.app/pricing

A permanent free plan for up to ten active members, then three paid plans priced per active member per month, then Enterprise, which is quoted. Bot accounts, guests and deactivated accounts are never counted as seats.

- **Free** — €0 up to 10 members. For a small team that wants the conversation encrypted without a purchase decision first.
- **Starter** — €6 per member / month. For a team past ten people that wants the conversation encrypted and nothing else switched on.
- **Team** — €11 per member / month. For organisations running the work itself in Enclessa, not only the talking.
- **Business** — €17 per member / month. For organisations that also run time, absence and personnel records here.
- **Enterprise** — Custom. For organisations that need the platform on infrastructure of their own — dedicated, in a region they name, still operated by us.

The free plan is described in full at https://enclessa.app/free.
Enterprise, and what a dedicated deployment is, at https://enclessa.app/enterprise.

## Security

URL: https://enclessa.app/security

What Enclessa does NOT have, stated plainly so it is not inferred otherwise:
- No certifications: Enclessa holds no ISO 27001, SOC 2, HIPAA or comparable certification. Anyone requiring one as a procurement gate should treat that as decisive today.
- No external security audit yet: The cryptography uses an audited library, OpenMLS, but Enclessa’s own implementation has not been through a third-party audit. That is planned work and is not finished work.
- No regional data residency: The hosted service runs in one European Union region. There is no choice of country within it. Where that is not sufficient, the Enterprise plan buys a dedicated deployment in a region you name, still operated and updated by us — the software itself is never handed over.
- No single sign-on yet: Sign-in is by email and password. Integration with an external identity provider, and SCIM provisioning, are planned enterprise work and are not available.
- Managed channels are readable by the server: That is deliberate — it is what makes search, retention and compliance export possible — but it means channel content is not protected the way a direct message is. Choose the room to match the sensitivity.

## By sector

URL: https://enclessa.app/solutions

- [Public sector](https://enclessa.app/solutions/public-sector) — Data that stays in the EU, an auditable record of who did what, and an exit that is an export rather than a negotiation.
- [Healthcare](https://enclessa.app/solutions/healthcare) — Clinical discussion in rooms the server cannot read, with operational channels that stay searchable and exportable.
- [Legal and advisory](https://enclessa.app/solutions/legal) — Privilege that survives a subpoena of the server, with the firm’s own operations kept searchable.
- [Engineering teams](https://enclessa.app/solutions/engineering) — Channels wired to the boards and repositories the work happens in, without shipping the backlog to a third party.

## By job

URL: https://enclessa.app/use-cases

- [Incident response](https://enclessa.app/use-cases/incident-response) — Run the incident in one channel, with the alerts, the call, the decisions and the timeline in the same place.
- [Onboarding a new colleague](https://enclessa.app/use-cases/employee-onboarding) — One record that provisions the accounts, the teams, the boards and the working time, instead of a checklist somebody executes by hand.
- [Board and works-council communication](https://enclessa.app/use-cases/confidential-leadership) — A conversation the platform operator cannot read, with no administrator override and no way to add a reader after the fact.
- [Client work with time against it](https://enclessa.app/use-cases/client-work) — A channel per client, a board for the work, and hours recorded against the project rather than reconstructed on the last day of the month.
- [Engineering work in one place](https://enclessa.app/use-cases/engineering-workflow) — The repository, the board and the conversation about them in the same product, so a card knows which discussion produced it.
- [Replacing a WhatsApp group](https://enclessa.app/use-cases/replace-whatsapp-group) — Move work off personal phone numbers into rooms with real accounts, real roles, and a leaving process that actually removes somebody.
- [Remote-first daily coordination](https://enclessa.app/use-cases/remote-coordination) — Written by default, with scheduled messages, threads and a call when writing has stopped working.
- [A data-subject access request](https://enclessa.app/use-cases/data-subject-request) — What Enclessa can produce about one person, what it cannot, and why the encrypted rooms are the honest part of the answer.

## Comparisons

URL: https://enclessa.app/compare

- [vs Microsoft Teams](https://enclessa.app/vs/microsoft-teams) — Where Teams gives you an ecosystem, Enclessa gives you a published architecture, standard encryption and data that stays in Europe.
- [vs Slack](https://enclessa.app/vs/slack) — Slack is the best-known chat product on the market. Enclessa is the one whose direct messages the operator cannot read.
- [vs Mattermost](https://enclessa.app/vs/mattermost) — Mattermost you run yourself. Enclessa we run for you, in Europe, with direct messages the operator cannot read.

## Migrating from another product

URL: https://enclessa.app/migrate

There is no automated importer. Migration is manual, and every guide below says so before it says anything else.

- [From Slack](https://enclessa.app/migrate/slack) — Map workspaces and channels onto teams and categories, decide which private conversations become encrypted rooms, and cut over on a date.
- [From Microsoft Teams](https://enclessa.app/migrate/microsoft-teams) — Untangle the parts that are really SharePoint and Exchange, rebuild the teams and channels, and plan the identity question early.
- [From Mattermost](https://enclessa.app/migrate/mattermost) — The closest structural match of the five, and the migration where the real question is whether you want to stop operating it yourself.
- [From WhatsApp](https://enclessa.app/migrate/whatsapp) — Getting work off personal phone numbers and personal devices, where the organisation has no copy and no way to end access.
- [From Discord](https://enclessa.app/migrate/discord) — Roles and categories map unusually well; the things to test are always-open voice and the fact that there is no server export.

## Glossary

URL: https://enclessa.app/glossary

- **Audit log** (https://enclessa.app/glossary/audit-log) — An audit log is an append-only record of who did what, to which object, and when — kept separately from application logs so that it can be relied on as evidence rather than read as debugging output.
- **Compliance export** (https://enclessa.app/glossary/compliance-export) — A compliance export is a bulk extraction of message and file records in a structured format that a supervision, archiving or e-discovery system can ingest, rather than one a person is expected to read.
- **Cross-signing** (https://enclessa.app/glossary/cross-signing) — Cross-signing is a scheme in which each person holds one identity key that signs certificates for their own devices, so that verifying a person once is enough to trust every device they own rather than verifying each device separately.
- **Data processing agreement (DPA)** (https://enclessa.app/glossary/data-processing-agreement) — A data processing agreement is the contract required by Article 28 of the GDPR between a controller and a processor, setting out what the processor may do with personal data, on whose instructions, with what security, and what happens at the end.
- **Data residency** (https://enclessa.app/glossary/data-residency) — Data residency is the requirement that data be stored and processed within a named geographic territory, usually a country or an economic area such as the European Union.
- **Data subject access request (DSAR)** (https://enclessa.app/glossary/data-subject-access-request) — A data subject access request is a demand by an individual, under Article 15 of the GDPR, to be told whether their personal data is being processed and to receive a copy of it together with information about how and why it is used.
- **DSGVO** (https://enclessa.app/glossary/dsgvo) — DSGVO is the German name for the GDPR — Datenschutz-Grundverordnung — and refers to exactly the same Regulation (EU) 2016/679, not to a separate German law.
- **End-to-end encryption** (https://enclessa.app/glossary/end-to-end-encryption) — End-to-end encryption is a design in which a message is encrypted on the sending device and decrypted only on the receiving devices, so that the server carrying it holds no key that can open it.
- **Forward secrecy** (https://enclessa.app/glossary/forward-secrecy) — Forward secrecy is the property that compromising a key today does not allow the messages sent before that compromise to be decrypted, because the keys that protected them have already been destroyed.
- **GDPR** (https://enclessa.app/glossary/gdpr) — The GDPR is Regulation (EU) 2016/679, the European Union law that governs the processing of personal data and applies to any organisation processing the data of people in the EU, wherever that organisation is established.
- **Legal hold** (https://enclessa.app/glossary/legal-hold) — A legal hold is an instruction that suspends the normal deletion of specified data because it may be relevant to litigation, an investigation or a regulatory request.
- **LiveKit** (https://enclessa.app/glossary/livekit) — LiveKit is an open-source WebRTC media server, licensed under Apache 2.0, that provides selective forwarding, room management, access tokens and recording for real-time audio and video applications.
- **Managed channel** (https://enclessa.app/glossary/managed-channel) — A managed channel is a room whose contents the server can read, which is what allows server-side search, retention rules, audit trails and organisation-wide export to operate on it.
- **MLS (RFC 9420)** (https://enclessa.app/glossary/mls) — MLS, or Messaging Layer Security, is the IETF standard published as RFC 9420 for end-to-end encrypted group messaging, designed so that adding or removing a member costs work proportional to the logarithm of the group size rather than to the group size itself.
- **Multi-tenancy** (https://enclessa.app/glossary/multi-tenancy) — Multi-tenancy is an architecture in which one running installation of an application serves many independent customer organisations, each of which sees only its own data.
- **OpenMLS** (https://enclessa.app/glossary/openmls) — OpenMLS is an open-source implementation of the MLS protocol written in Rust, developed in the open by contributors from Phoenix R&D, Wire and Cryspen, and subjected to external security review.
- **Post-compromise security** (https://enclessa.app/glossary/post-compromise-security) — Post-compromise security is the property that a conversation heals after a device is compromised, so that once the compromised device is removed and the group re-keys, the attacker who held its keys can no longer read new messages.
- **Retention policy** (https://enclessa.app/glossary/retention-policy) — A retention policy is a rule stating how long a category of data is kept before it is deleted, applied automatically rather than left to somebody remembering.
- **Room mode** (https://enclessa.app/glossary/room-mode) — A room mode is the fixed property of a conversation that decides whether the server can read its contents, chosen when the room is created and never changed afterwards.
- **Safety numbers** (https://enclessa.app/glossary/safety-numbers) — A safety number is a short string derived from the public keys of both sides of an encrypted conversation, which the two people compare through a separate channel to confirm that no third party has interposed itself.
- **SCIM** (https://enclessa.app/glossary/scim) — SCIM is an open standard, published as RFC 7643 and RFC 7644, that lets an identity provider create, update and deactivate user accounts in another application automatically over a REST API.
- **Seat-based pricing** (https://enclessa.app/glossary/seat-based-pricing) — Seat-based pricing charges a fixed amount for each person who can use a product, so the bill is the seat price multiplied by the number of people rather than by how much they use it.
- **SFU (Selective Forwarding Unit)** (https://enclessa.app/glossary/sfu) — A selective forwarding unit is a media server that receives one stream from each participant in a call and forwards copies to the others, without decoding or mixing them.
- **Single sign-on (SSO)** (https://enclessa.app/glossary/single-sign-on) — Single sign-on is an arrangement in which one identity provider authenticates a person once and then vouches for them to other applications, so that each application never handles their password.
- **Subprocessor** (https://enclessa.app/glossary/subprocessor) — A subprocessor is a third party that a processor engages to carry out part of the processing of personal data on the controller’s behalf — a hosting provider, a payment provider or an email relay, for example.
- **Tenant isolation** (https://enclessa.app/glossary/tenant-isolation) — Tenant isolation is the guarantee that no request made by one customer organisation can read or change any data belonging to another, enforced by the system rather than by convention.
- **WebRTC** (https://enclessa.app/glossary/webrtc) — WebRTC is the browser standard for real-time audio, video and data connections, which lets a web page carry a call without a plugin and encrypts every media stream by default.
- **Zero-knowledge** (https://enclessa.app/glossary/zero-knowledge) — Zero-knowledge is a term from cryptography for a proof that convinces a verifier a statement is true while revealing nothing else, and it is also used loosely in marketing to mean that a provider cannot read customer data — two things that are not related.

## Trust, status and change

- Trust centre, for procurement and data protection: https://enclessa.app/trust
- Service status and incident policy: https://enclessa.app/status
- What has shipped, and when: https://enclessa.app/changelog
- What is being built, and what is deliberately not: https://enclessa.app/roadmap

## Frequently asked questions

### Is Enclessa in beta?
Enclessa is in open beta: anybody can create a workspace today, without an invitation and without a waiting list. The platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is on this site is what is built: the messaging, encryption, calls and modules described here work today, the limits are stated on the page that claims the capability, and the roadmap says what is still missing. Beta does not mean the free plan expires or that data is treated as disposable — a full organisation export is available throughout.

### What is Enclessa?
Enclessa is a hosted collaboration platform for organisations, currently in open beta, combining team messaging with channels and threads, end-to-end encrypted direct messages, video calls with screen sharing, and twelve optional modules covering boards, GitHub, projects, customers, contracts, bookings, employee cards, mail, time tracking, personnel records, a ledger connector and an assistant. It is a commercial software-as-a-service product, run in the European Union by a German company, with a free plan and paid plans priced per member.

### Do I need to install or host anything to use Enclessa?
No, and there is no version of Enclessa you can install. It is a hosted service: you create a workspace, it is reachable at your-team.enclessa.app, and we operate the infrastructure. Organisations that need a deployment of their own buy it on the Enterprise plan, where we run dedicated infrastructure for them rather than handing over software to run.

### Where is Enclessa hosted and who is the seller?
Enclessa is hosted in a single European Union region and sold by a company established in Germany, so EU VAT applies and is shown separately on every invoice.

### Is Enclessa open source?
No. Enclessa is a commercial software-as-a-service product and the source is not published. What is published is the part a buyer actually has to check: the architecture, the data model, the OpenAPI surface, the subprocessor list and the encryption design. The encryption itself is MLS per RFC 9420 through OpenMLS, an open standard and an audited open-source implementation, so the guarantee does not rest on anything of ours being trusted.

### Is there a free plan?
Yes. The Free plan is permanent rather than a trial: a small team gets channels, threads, end-to-end encrypted direct messages and video calls without a payment card. Paid plans add the optional modules, longer retention and higher limits.

### Which parts of Enclessa are end-to-end encrypted?
Direct messages and group direct messages are always end-to-end encrypted using MLS per RFC 9420. Channels are managed, meaning the server can read them, which is what makes full-text search, retention policies and compliance export possible.

### Can several organisations share one account?
Yes. One account can hold a membership in several organisations and switch between them from the sidebar without signing in again, seeing in each exactly what that membership allows and nothing of the others.

### Which clients does Enclessa have?
The web application is available today and a macOS desktop application is in development. Mobile applications for iOS and Android are planned and not yet available.

### How much does Enclessa cost?
Enclessa has a free plan and three paid plans priced per active member per month, differing by which modules are included. Bots, guests and deactivated accounts are not counted as seats. Enterprise is quoted rather than listed, because it includes a dedicated deployment run for the organisation. See the pricing page for the current tiers.

## Full question index

https://enclessa.app/faq carries every question and answer on the site in one page.

## About the company

- Who builds Enclessa, and the limits it publishes about itself: https://enclessa.app/about
- Why it exists, and who it is not for: https://enclessa.app/why-enclessa
- How to reach a person: https://enclessa.app/contact
- Every page on the site, by the question it answers: https://enclessa.app/resources

Enclessa is operated by Quavon UG (haftungsbeschränkt), Langbehnstraße 39, 83022 Rosenheim, Deutschland — register HRB 35427 at Amtsgericht Traunstein, VAT DE463525246. The service and its data are operated by netcup GmbH in Karlsruhe, Germany.

## Legal documents

German is the operative language; the English versions say so in their first paragraph.

- imprint: https://enclessa.app/legal/imprint — Deutsch: https://enclessa.app/de/rechtliches/impressum
- privacy: https://enclessa.app/legal/privacy — Deutsch: https://enclessa.app/de/rechtliches/datenschutz
- terms: https://enclessa.app/legal/terms — Deutsch: https://enclessa.app/de/rechtliches/agb
- dpa: https://enclessa.app/legal/dpa — Deutsch: https://enclessa.app/de/rechtliches/auftragsverarbeitung

## Deutsch

The site is published in English and German. German covers the home page, the pricing page and the four legal documents; every other page is English only.
- https://enclessa.app/de — English: https://enclessa.app
- https://enclessa.app/de/preise — English: https://enclessa.app/pricing
- https://enclessa.app/de/sicherheit — English: https://enclessa.app/security
- https://enclessa.app/de/rechtliches/impressum — English: https://enclessa.app/legal/imprint
- https://enclessa.app/de/rechtliches/datenschutz — English: https://enclessa.app/legal/privacy
- https://enclessa.app/de/rechtliches/agb — English: https://enclessa.app/legal/terms
- https://enclessa.app/de/rechtliches/auftragsverarbeitung — English: https://enclessa.app/legal/dpa