Enterprise · quoted, not listed

A deployment that is yours alone, run by us

Talk to us about a deployment Compare it with Business

Enclessa Enterprise is a dedicated deployment of the hosted service, which is in open beta: your own database, object storage and media nodes, in a European region you name, with no shared tenancy. Enclessa operates and updates it, adds a named contact with agreed response times, security advisories ahead of public disclosure, and the procurement, compliance and architecture documentation a review needs. Enterprise is quoted, not listed.

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.

At a glance

Release stage: Open beta, like the shared service
What it is: A dedicated deployment of the hosted service
Tenancy: Yours alone — own database, storage and media nodes
Region: One you name; still operated and updated by us
What it is not: Not a licence, not an installer, not air-gapped
Support: Named contact and an escalation path, agreed response times
Commercial terms: Annual agreement, quoted rather than listed

What does a dedicated deployment actually consist of?

The same platform every other customer runs, on infrastructure that belongs to your agreement and to nothing else. Nothing is shared with another organisation at any layer that holds data: the database is yours, the object storage is yours, and the media nodes that carry video calls are yours. It runs in a European region you name rather than in the one shared region the standard plans use.

Your own PostgreSQL database, with no rows belonging to anybody else
Your own object storage for files, attachments and generated exports
Your own media nodes for video calls and screen sharing
A region you name, chosen before the deployment is built
Every module included: all twelve, from boards and GitHub to contracts, mail and the ledger connector

Is Enterprise a licence to run Enclessa ourselves?

No, and it is worth being blunt about it because in this category the word usually implies the opposite. Enclessa is not distributed to anybody. There is no source code release, no installer, no container image handed over and no self-hosted licence at any price. An Enterprise deployment is infrastructure that we build, operate, monitor, patch and upgrade — the isolation is dedicated, the operation is not transferred. If running the software on machines under your own control is a hard requirement, Enclessa cannot meet it and an open-source platform should be on your shortlist instead.

No source code, no binaries and no images are released to a customer
Updates are applied by us, on the same release train as the shared service
Monitoring, backups, certificates and incident response stay with us
There is no air-gapped or disconnected installation option

What comes with it besides the infrastructure?

The parts of a vendor relationship that matter after signature rather than at it. An Enterprise agreement names a contact and an escalation path with response times written into it, rather than a shared inbox and a best effort.

A named contact and an escalation path, with response times agreed in the contract
Security advisories ahead of public disclosure, so you can plan a window rather than react to one
Procurement, compliance and architecture documentation prepared for a review team
A deployment review before go-live, covering configuration, roles and retention
Recovery drills, so the backup story is something that has been executed rather than described

How is an Enterprise deployment bought?

By talking to us, because the price depends on the region, the size and the commitments, and a number invented on a pricing page would be a number we could not honour. The commercial shape is fixed: an annual agreement, quoted per organisation, invoiced in euro by a seller established in Germany with EU VAT shown separately. The technical shape is settled before anything is built — the region, the expected member count, the modules you want switched on, and the retention and legal-hold rules the deployment starts with.

Tell us the region, the approximate member count and the review process you have to satisfy
We answer with an architecture and a quotation, and the documentation your reviewers need
The deployment is built and reviewed with you before anybody signs in

What Enterprise still does not include

Enterprise does not come with a certification. Enclessa holds no ISO 27001, SOC 2 or comparable certificate, and a dedicated deployment does not create one.
Enterprise does not come with an external security audit. The cryptography uses an audited open-source library, OpenMLS, but Enclessa’s own implementation has not been audited by a third party on any plan.
Enterprise does not add single sign-on. Sign-in is by email and password, and there is no external identity-provider integration or SCIM provisioning yet.
Enterprise is not an air-gapped or disconnected installation, and it is not a licence: the software is never handed over, and we retain operation of the deployment.
Enterprise does not change what the product does. It is the same platform with the same features as the Business plan, on infrastructure that is yours alone.

Plans and pricingWhat the standard plans include, and where Business ends and Enterprise begins.Read more Security and encryptionTenant isolation, MLS, the control plane that cannot read content, and the certifications we do not hold.Read more Why EnclessaThe positioning argued objection by objection, including where Enclessa is the wrong choice.Read more Compare the alternativesAgainst Microsoft Teams, Slack and Mattermost, with the exit and the licence model in every table.Read more Evaluate on the free plan firstTen members, encrypted direct messages and video calls, before any procurement conversation starts.Read more Who builds and operates itThe company behind the service, and the principles the platform is held to.Read more

Procurement

Enterprise: what a review team asks first

How is Enclessa Enterprise billed?

As an annual agreement, quoted per organisation rather than listed, and invoiced in euro by a seller established in Germany with EU VAT shown separately. The quotation depends on the region, the member count and the commitments in the contract, which is why there is no price on the pricing page.

Do you sign a data processing agreement?

Yes. Enclessa acts as a processor for the content your organisation puts into the platform, and a data processing agreement is part of the standard paperwork on every plan, Enterprise included. It is available for review before signature rather than after it, and an Enterprise agreement can be read by your own counsel alongside it.

Which subprocessors does Enclessa use?

The current list is published on the trust centre, with the role each one performs and where it operates. A dedicated deployment narrows that list to the providers involved in the region you choose, and the agreement covers how a change to it is notified.

Can we choose the country our data is stored in?

On the standard plans, no: the hosted service runs in one European Union region and there is no choice of country within it. That choice is precisely what Enterprise buys — a dedicated deployment in a region you name, operated and updated by us.

What happens to our data if we leave?

You export it first. A full organisation export in open formats is available at any time, on every plan, and the data model and the OpenAPI surface are documented so the export can be read and reloaded elsewhere. Once the export is complete the dedicated deployment is decommissioned and its data purged, on a schedule written into the agreement.

Can we run Enclessa on our own infrastructure under an Enterprise agreement?

No. Enclessa is never distributed and there is no licence to install it, so an Enterprise deployment is dedicated infrastructure that we operate rather than software you receive. Organisations whose requirement is to run the software themselves should look at an open-source platform such as Mattermost instead.

Tell us the region and the review you have to pass.

An Enterprise deployment starts with a conversation rather than a checkout: the region, the member count, the modules you need switched on, and the documentation your reviewers require.

Create your workspace See pricing

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