VOOM

VOOM Secure Collaboration

The organisation decides who is in the room, not the server

Data sovereignty instead of server dependency: server-blind communication for the highest security requirements – for government, defence, critical-infrastructure operators and regulated companies. Works on its own or as a sovereign complement to Microsoft 365.

  • Server-blind: No server sees plaintext
  • Signed: Entry only with the organisation’s signature
  • Sovereign: Operated in Switzerland, keys stay with the customer

SWISS BUILT / SWISS OWNED

Why now

Digital trust depends on things you cannot verify

Encryption protects data. But organisations still have to trust operators, administrators, identity systems and permission databases.

Sovereignty

Control over sensitive data and infrastructure is becoming a strategic issue.

Regulation

Switzerland’s Information Security Act, the FADP and FINMA rules, plus NIS2 and DORA in the EU, increase management accountability.

Crypto lifecycle

Crypto-agility is needed before the move to post-quantum algorithms becomes urgent.

Today: administrative trust

Trust in operators

  • Identitymanaged by third parties
  • Serversrun by providers
  • Permissionsset by administrators
  • Contentdependent on operators

You have to trust the system.

With VOOM: cryptographic trust

Trust in mathematics

  • Identitysigned by the organisation
  • Serversonly see encrypted content
  • Permissionsenforced by cryptography
  • Contentreadable only on authorised devices

Sovereign, verifiable and controlled by the organisation.

How VOOM works

Confidentiality and control, without the trade-off

Signed members and devices inside the organisation’s room; an unsigned device stays outside; the server only sees encrypted content; after a signature is revoked, a key rotation locks the device out.not signedAccess denied9f3a c71e 04bde2d8 5a10 7c3fb46e 19fa d02cServer: onlyencrypted contentThe organisation’s keySignature revoked
  • not signed
  • Server: encrypted content only
  • The organisation’s key
  1. The organisation signs every member and every device with its own key.
  2. Unsigned devices cannot get in. Not even the operator can add anyone without the organisation’s signature.
  3. Servers transport and synchronise content in encrypted form only.
  4. The organisation can revoke a signature, for example if a device is lost or someone leaves. With the key rotation, the device is locked out of new content.

The difference

Comparison of typical product categories with VOOM
CriterionSuitesBusiness messengers
Central administrationYesYesYes
Server has no access to plaintextNot by defaultYesYes
Organisation signs members and devices with its own keyNoUser-basedYes

A question for your evaluation

Who signs which people and devices may enter your rooms? And can the operator add anyone without your signature?

Simplified positioning of typical product categories based on public vendor documentation, as of October 2026.

Six reasons for VOOM

Trust you can verify

Server-blind

Plaintext and keys exist only on authorised devices. There is no central store of readable data.

No silent additions

Neither servers nor operators, not even ENSIGNUM, can add anyone to a room without the organisation’s signature.

Permissions by key

Policies, roles and revocation are enforced cryptographically. Revoking access means rotating keys.

Device-bound identity

Access only from a registered device; lost devices are locked out and keys rotated.

Sovereign operation

Operated on premises, with a Swiss partner or with a carrier. Control of the keys stays with the customer.

Crypto-agile

Algorithms are versioned and interchangeable. Post-quantum algorithms can be introduced without re-architecting the platform.

Trust Layer: platform and roadmap

From room to case: everything is a message

Today VOOM protects the room. Next, the room becomes a protected case: messages, documents, tasks, approvals, evidence and AI jobs in one context, under one policy and end-to-end encrypted.

One protected case in the middle; around it people, devices, documents, evidence, approvals and AI jobs – all messages in the same context.Protected caseone context, one policyPeopleDevicesDocumentsEvidenceApprovalsAI jobs

Case apps from signed templates

Forms, roles, approvals and AI jobs are declared, versioned and signed. AI drafts, a person releases.

AI as a controlled participant

A visible recipient with its own identity and a limited mandate. Proposals stay proposals until a person approves.

First reference processes

Contract review with external counsel, M&A data rooms and incident rooms, with or without Teams and AI.

Today

Chat, email, files and approvals run separately, and context gets lost.

With VOOM

One protected case for messages, documents, approvals and AI jobs.

Stages

  1. VOOM

    2026–2028

    Secure communication, signed members and devices, Safe Room

    Beta today, Release 1.0 2027

  2. VOOM Health

    from 2027

    Clinical communication, tumour boards, telemedicine

    Pilots planned

  3. Identities and cases

    2027–2028

    Cases, four-eyes approvals, case apps

    planned

  4. AI and agents

    2028–2029

    Knowledge and process assistance, controlled AI actions

    planned

  5. Data, DLT and ecosystem

    from 2029

    Sovereign data exchange, audit trail on DLT, templates and SDK

    planned

Stages 2 to 5 are planned and released only after product, security and customer reviews. Planned functions are not available; scope depends on the release, details on request.

Use cases

For communication that has to stay protected

Government and administration

Protected teams, crisis and situation rooms

Defence and security

Protected mobile communication with central device control

Critical infrastructure

Crisis and command communication, including during reportable incidents

Healthcare

Clinical communication, tumour boards, referral networks

Finance and legal

Confidential deal and client communication

Carriers and providers

Secure communication as a service for business customers

One communication layer for the whole organisation

Sovereign operation, end-to-end encryption, membership signed by the organisation. On its own or as a complement to Microsoft 365.

Contact

Get to know VOOM

Book a demo. We will show you how VOOM would work in your organisation.

  • Live demo, on site or online
  • Questions on architecture, operation and integration
  • Under NDA if required
Dr. Stefan Grimm

Your contact

Dr. Stefan GrimmCo-founder and interim CEO, ENSIGNUM AG, Bern

www.voom.ch / www.ensignum.ch

Book a demo
Book a demo