Skip to content

What we’re building, and what we won’t

Enclessa is in open beta. Here’s what we’re working on, what comes next and the ideas we’re exploring.

Updated

See what shippedSuggest a feature

In progress

2

Desktop apps · Android app

Next

3

Archive formats, audit log delivery and legal hold marker · Larger calls and downloadable recordings · Service reliability

Exploring

5

Independent security and accessibility reviews · Partner platform review · API documentation and client libraries · Future encryption standards · Search at larger scale

The board

In progress, next, exploring

In progress

2

In development now.

  1. 01Desktop apps

    macOS and Windows apps are available. Desktop screen sharing and a signed Windows installer are still to come.

  2. 02Android app

    The iOS app is in the App Store for iPhone and iPad. Android has not started.

Next

3

Our next priorities.

  1. 01Archive formats, audit log delivery and legal hold marker

    Archive-platform export formats, audit log delivery to your syslog or HTTPS endpoint, and a platform-wide legal hold marker. Per-team and per-room retention and compliance exports exist today.

    About compliance exports

  2. 02Larger calls and downloadable recordings

    Test larger calls and add downloadable recordings. Call capacity is not yet measured, and recordings have no downloadable file today.

    What calls do today

  3. 03Service reliability

    Resilience to infrastructure failure and load testing. No measured availability or capacity figures exist yet.

    Service status

Exploring

5

Ideas and improvements we’re evaluating.

  1. 01Independent security and accessibility reviews

    An external security audit, penetration test and accessibility audit. None is commissioned yet.

    Security at Enclessa

  2. 02Partner platform review

    Third-party apps install today. An external audit and penetration test of the partner platform are still to come.

    Integrations that exist today

  3. 03API documentation and client libraries

    Developer documentation and client libraries for integrating with Enclessa.

  4. 04Future encryption standards

    Post-quantum encryption as standards mature, and an independently verifiable key directory. Neither exists today.

    How encryption works today

Ruled out

Frequently asked for, and deliberately not planned

Decisions with reasons, not gaps waiting for a sprint.

  1. Encrypted channels by default

    Channels are managed by default so search, retention and export work. Encrypted channels can be permitted per channel, and give those up.

  2. Access to encrypted conversations

    No hidden access. The server holds no room keys, and any compliance recipient would be visible to participants.

  3. Managed hosting

    No self-hosting, source licences or air-gapped installs. Enterprise gets a dedicated deployment operated by Enclessa.

  4. Data location

    Standard plans use one EU region. A specific country means a dedicated Enterprise deployment.

  5. More than one domain

    An enclessa.app subdomain plus one domain you own. A second is not planned.

  6. Document editing

    Files are stored, versioned and viewed; Spaces has versioned pages. Live co-editing and spreadsheets are not planned.

  7. Room encryption settings

    Fixed at creation, so messages keep the access rules they were sent under.

FAQ

Roadmap questions

  • Yes. Connect your identity provider over OIDC or SAML, provision members with SCIM and require a second factor across your organisation.

  • The changelog lists released updates. The feature pages describe what you can use today.

  • Yes. Use the contact page to tell us what your team needs and how you would use it.

Bring your team over this afternoon

Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.

For businesses and organisations only — not available to consumers.

Create your organisationCompare plans