Skip to content
Enclessa
Get started

Roadmap

What is being built, and what never will be

Enclessa is in open beta, and this roadmap sets out what Enclessa has in progress, what comes next and what is under consideration, in order and without dates. A roadmap is a statement of intention rather than a commitment: nothing on this page is a contractual date, an availability guarantee or a reason to sign. The most useful section is the last one, which lists the capabilities Enclessa is asked for repeatedly and has decided not to build, with the reason for each — including end-to-end encryption of group channels and self-hosting.

Open betaThe 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 still being built.

Read this before you read the rest

A roadmap is a statement of intention, not a commitment. Nothing on this page is a contractual date, an availability guarantee, or a reason to sign a contract you would not otherwise sign. There are no dates here at all — only ordering, and ordering changes when something more important arrives. If a capability has to exist before you can buy, treat it as absent until it appears on the changelog.

At a glance

Dates given
None. Ordering only
Status of this page
An intention, never a commitment
In progress
3 items, none available yet
Next
6 items, in roughly this order
Considered
5 items, any may be dropped
Not planned
7 frequently requested things, with reasons

In progress

Work that has started and is partly built. Nothing here is available to use, and the parts already written are recorded in the build record rather than claimed on a feature page.

The macOS application

The application shell is built: several accounts, the windows, the native menus, deep links and the tray. What is missing is the part that makes it installable — a build signed with a real developer certificate and put through notarisation, which has never happened because no certificate exists on the build machine. Screen sharing through the native capture API is also outstanding. Until both are done, Enclessa is a web application and says so.

MASTERPLAN §23 phase 3a; docs/PROGRESS.md phase 3a, steps 3a.1 and 3a.3

The iOS and Android applications

The shell, the sign-in, the channel list, the transcript, the composer and live message delivery are written and bundle for both platforms. No native build has ever been produced and nothing has been run against a live API, so nothing is installable. Offline storage, push notifications, encrypted rooms on mobile, calls and screen sharing are all still to come.

MASTERPLAN §23 phase 3b; docs/PROGRESS.md phase 3b, steps 3b.4–3b.9

Next

The work that follows what is in progress, in roughly this order. Ordering is an intention and it changes when something more important arrives.

Plans, seats, trials and payment

There is no billing system. Plans and subscriptions, the seat count that feeds which modules an organisation may install, trials, the payment provider and the path back from a failed payment are all still to be built. This is why the prices published today are marked as placeholders and why the Free plan needs no payment card — there is nothing to take one with.

MASTERPLAN §23 phase 7f; docs/PROGRESS.md phase 7f, steps 7f.1–7f.7

See the current pricing

Single sign-on and SCIM provisioning

Sign-in is by email address and password today. The foundation is built: sign-in can already accept an assertion from an external identity provider and turn it into the same account, membership and session a password produces. No identity provider is connected to it yet — there is no OIDC or SAML integration — and automated provisioning and deprovisioning over SCIM and enforcement of multi-factor authentication across an organisation have not started. An organisation for which single sign-on is a procurement gate should treat Enclessa as unsuitable until this ships.

MASTERPLAN §23 phase 5; docs/adr/0155

What single sign-on is

Compliance export, retention per channel, audit log export

A full organisation export exists today. What does not exist is the supervision half: a compliance export in the formats archiving platforms ingest, retention rules at team and channel level rather than per organisation, export of the audit log to an external sink, and a platform-wide legal hold marker. Each is separate work and none of it is available.

MASTERPLAN §15 and §23 phase 5; docs/PROGRESS.md phase 7e

What a compliance export is

Proving call scale, and recordings you can download

The instrument for the fifty-person call target is built and the test has never been run, so Enclessa publishes no measured figure for how large a call can be. Recording exists for managed rooms and produces a record in the platform rather than a file anybody can download; the media pipeline that would produce one is deferred work.

docs/PROGRESS.md phase 4, steps 4.13 and 4.14

What calls do today

Guest accounts and reusable permission schemes

Everybody in an organisation today is a member of it. Guest accounts with restricted visibility across named rooms, named permission schemes that teams stay bound to rather than each configuring itself, and the delegated administrator roles that go with them are enterprise work that has not started.

MASTERPLAN §15 and §23 phase 5

The high-availability deployment profile

The hosted service runs on a documented deployment with a scripted procedure and a runbook. The profile above it — database failover, a clustered message layer on dedicated nodes, separate media and recording nodes, and the capacity numbers that come from actually load-testing them — is planned and not built. No availability figure is published, and none will be until it is measured.

MASTERPLAN §21.1 and §23 phase 5

The operational position today

Considered

Things Enclessa intends to do and has not committed to the shape of. Anything in this group may be dropped, and several items depend on decisions nobody has taken yet.

An external security and cryptography audit

Enclessa has had no third-party security audit and holds no certification. The cryptographic library it uses has been audited; Enclessa’s own integration of it has not. An external audit, a penetration test and an accessibility audit are all intended, and none has been commissioned, so no date and no scope can honestly be given for them.

MASTERPLAN §23 phase 6

What Enclessa does not hold

Third-party apps and a public app platform

The marketplace today installs Enclessa’s own modules. The partner half — Enclessa acting as an OAuth2 provider, an app registry with reviewed and immutable versions, consent that a new permission has to re-ask for, signed event delivery with retries, and a sandbox to submit against — is designed and not built. A deliberate constraint of that design: no partner JavaScript ever runs inside Enclessa.

MASTERPLAN §23 phase 6; docs/adr/0016

Integrations that exist today

Published API documentation and client libraries

The whole API is already described by an OpenAPI document and a TypeScript client is generated from it on every build. What is not published is documentation written for somebody outside the project, and client libraries for other languages. Both are intended.

MASTERPLAN §23 phase 6

Post-quantum ciphersuites and key transparency

MLS gains post-quantum ciphersuites as the relevant drafts become standards, and Enclessa intends to enable them at that point rather than before — a bespoke pre-standard implementation would be exactly the kind of home-grown cryptography this product avoids. Key transparency, which would make the key directory itself auditable, is under evaluation and no decision has been taken.

MASTERPLAN §23 phase 6

How encryption works today

A dedicated search engine, and a different orchestrator

Search runs on PostgreSQL full-text today, which is enough at current sizes and will not be at every size. A dedicated search engine is an option held open for the largest deployment profile. So is moving that profile from Docker Swarm to Kubernetes, which is written up as a conditional decision rather than a plan, because it is only worth doing when several operational needs arrive at once.

MASTERPLAN §4.1, §21.2 and §23 phase 6

Not planned, and why

This is the most useful section of the page. Everything below is asked for repeatedly, and every answer is a decision rather than a backlog position — so you can stop waiting for it and decide now whether Enclessa is the wrong product for you.

End-to-end encryption of group channels

Channels are readable by the server on purpose, because that is what makes search, retention, compliance export and audit possible. Encrypting them would remove all four and there is no arrangement that keeps both. The route Enclessa would take if a customer needed encrypted rooms with oversight is a compliance recipient that is visible to everybody in the room as an additional member — never a hidden one. End-to-end encryption stays where it belongs: direct messages and group direct messages.

MASTERPLAN §3 and §15

Any covert access to encrypted conversations

Enclessa will not build a reader that participants cannot see, for a customer, for a regulator or for itself. A covert reader is a backdoor whichever authority requests it, and its existence would make every other statement on this site unverifiable. The architecture is the enforcement: the server holds no key for an encrypted room, and the operator surface is technically prevented from importing any code that could read content.

MASTERPLAN §15; docs/PROGRESS.md phase 7d, step 7d.8

Self-hosting, a source licence, or an air-gapped install

Enclessa is a hosted service and is never handed over. There is no open-source release, no published source, no self-hosted licence and no air-gapped deployment. What exists for a buyer who cannot use the shared installation is Enterprise: a dedicated deployment of the same hosted service, in a region the customer names, operated and updated by Enclessa. That is a different arrangement from self-hosting and Enclessa does not describe it as one.

MASTERPLAN §1; docs/design/saas.md §8

Choosing a country for your data on the standard plans

The hosted service runs in one European Union region, and there is no region picker. An organisation that must keep data inside a named country — which happens in parts of the public sector and in healthcare — cannot satisfy that with the standard plans and should be talking about a dedicated deployment instead. Enclessa would rather say that in the first conversation than in the sixth.

MASTERPLAN §21.1; docs/design/saas.md

Custom domains for your workspace

Every organisation is reached at its own subdomain of enclessa.app, issued under a single wildcard certificate. Custom domains would mean per-customer certificate issuance and renewal, and a class of failure that takes a customer offline for reasons unrelated to the product. It is a decision rather than a backlog item.

MASTERPLAN §15; docs/adr/0037

Document co-authoring, a wiki, or spreadsheets

Files are stored, scanned, versioned, searched and displayed. They are not edited in Enclessa, and there is no collaborative document editor, wiki or spreadsheet. Building one well is a product in itself, and building one badly is worse than linking to the tool a team already uses.

docs/PROGRESS.md; the messaging feature page limits

Converting a room between encrypted and managed

A room’s mode is fixed when it is created. Converting an encrypted room to a readable one would expose history written under a different promise, and converting a readable room to an encrypted one would leave its existing history permanently unopenable while appearing to protect it. Neither is a setting worth offering, so neither exists.

MASTERPLAN §3

What exists today

The feature pages describe each capability as it stands, each ending with what it does not do. The changelog records what shipped and when it was verified, and the security page leads with the certifications Enclessa does not hold. For a dedicated deployment in a region you name, see Enterprise.

Questions

About this roadmap

Why does the Enclessa roadmap have no dates?

Because a date on a roadmap is read as a commitment, and Enclessa cannot commit to one. The page gives ordering instead, which is the part that is actually knowable, and states that ordering changes when something more important arrives.

When will Enclessa support single sign-on?

There is no date. The foundation is built — sign-in can accept an assertion from an external identity provider — but no identity-provider integration over OIDC or SAML exists yet, SCIM provisioning has not started, and sign-in today is by email address and password. An organisation for which single sign-on is a procurement gate should treat Enclessa as unsuitable until it ships rather than plan around it.

Will Enclessa end-to-end encrypt group channels?

No. Channels are readable by the server on purpose, because that is what makes search, retention, compliance export and audit possible, and encrypting them would remove all four. End-to-end encryption covers direct messages and group direct messages, and which mode a room uses is shown in the room itself.

Can I self-host Enclessa or buy a source licence?

No. Enclessa is a hosted service and is never distributed: there is no open-source release, no published source, no self-hosted licence and no air-gapped deployment. The Enterprise plan buys a dedicated deployment of the same hosted service in a region you name, operated and updated by Enclessa, which is a different arrangement from self-hosting.

Can I request a feature that is not on this roadmap?

Yes, through the contact page. What will not happen is a feature being added to this page because somebody asked for it — an item appears here when the work is genuinely intended, which is what makes the list worth reading.

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.

Create your workspaceSee pricing

Open beta. Free plan, no payment card to start.