Sovereign applications · Roadmap

Collaborate in real time inside the boundary you define.

Give teams governed channels, direct conversations, voice, video meetings and file exchange in a customer-operated service connected to organisational identity and knowledge.

Status: Roadmap. This application is being developed for open-source release. Its repository, OSI-approved software licence, model-specific terms, version, provenance and supported deployment modes will be published with the applicable release.

Planned replacement scope

Which enterprise software category is this designed to replace?

Roadmap scope: designed to replace or consolidate enterprise team messaging, chat, voice and video conferencing, online meeting and collaboration platforms. Adoption would validate federation, accessibility, call quality, moderation, retention, identity and incident-response requirements.

Core capabilities

Designed around accountable organisational work.

Exact coverage, deployment requirements and limitations are documented for the selected version and use case.

Channels and direct conversations

Organise team and one-to-one communication with role-aware access, search and customer-defined retention.

Voice, video and meetings

Support browser-based calls, scheduled meetings, screen sharing and collaborative sessions within the deployment boundary.

Governed file exchange

Share files in context and move records that require lasting governance into the Document Management System.

Operational control

Define identity, federation, guest access, moderation, retention, export and service-continuity policies.

Roadmap · Shared application capability

Customer-controlled improvement loop

Planned local analysis of authorised service and collaboration signals can propose better channel structure, meeting support and operational configuration under customer-defined evaluation, approval and rollback controls.

Explore the SovereignEU Improvement Loop

Product boundary

Conversation becomes useful context deliberately

Identity & Access Management controls participation. Mail & Calendar coordinates scheduling. The Document Management System retains governed records, while Knowledge Management receives only reviewed and approved reusable information.

Adoption outcome

Start with defined teams and communication rules

Pilot representative conversations and meetings, verify accessibility, quality, retention, export and escalation, then extend the service through an approved migration plan.

Sovereignty matrix

Evaluate the deployment across six dimensions.

Product-specific answers are established through the deployment architecture and dated evidence record.

DataOperationalTechnologyJurisdictionKnowledgeExit
Review the trust model

A practical first step

Start with defined teams and communication rules

Pilot representative conversations and meetings, verify accessibility, quality, retention, export and escalation, then extend the service through an approved migration plan.

Plan a secure collaboration use case