Secure Communications a State Actually Owns

Public-safety agencies coordinate on consumer messaging apps because nothing else is on the phone in their hand. Sover is the alternative that a ministry can host itself, rebrand, and read the source code of.

What It Is

Your Sovereign Unified-Communications Platform

Sover is a secure, user-hosted unified-communications platform built for organizations that cannot accept a SaaS messaging tool: government agencies, law enforcement, critical-infrastructure operators, and regulated enterprises. It provides end-to-end encrypted messaging, voice and video calls, group chats and channels, video sharing, workspaces, federation across independent deployments, bots, and LLM integrations.

It runs on-premises or in a private cloud, handles over 1,000 messages per second and supports hundreds of thousands of users, on Windows, macOS, Linux, Android, iOS, and the browser, with a Microsoft Outlook plugin. It is source-code licensable and rebrandable, so a sovereign customer can operate it under its own name and inspect what it is running.

Inside IREX deployments Sover is also the secure front end to the platform: alerts arrive there, evidence is uploaded there, and Ask IREX answers natural-language queries there.

Capability

What It Does

Messaging, Voice, and Video

One-to-one and group messaging, channels, voice and video calling, video sharing, and workspaces for standing teams.

Layered Encryption

TLS 1.2 or higher in transit, encryption at rest server-side, plus application-layer session-key and per-file encryption. A file key is never stored on the server.

Federation, on Your Terms

Independent deployments peer with each other, encrypted end to end so intermediate servers cannot read content. Closed-federation mode restricts peering to whitelisted servers.

Source-Licensable and Rebrandable

Sovereign customers license the source code and operate the platform under their own marks.

Bots and Integrations

A bot platform with webhooks and a REST API, which is how an external system posts into a channel. The IREX alarm notifier is one of those bots.

Administered Centrally

Back-office administration, audit trails, and role-based controls built in rather than bolted on.

IREX and Sover

What the Two Do Together

A public-safety program buys the two together rather than integrating a messenger afterwards, and this is what the pairing does once both are running.

Get Real-Time Alerts in Group Chats

Switch on messenger notifications for an alarm monitor and the monitor gets a chat of its own, with the authorized users already in it. Every event that lands on that monitor arrives as the event snapshot, the event name, the camera, the extras that apply — a plate number, say — the location, and a link that plays the event back in the IREX player. Members comment, forward the alert and upload media of their own, so the channel becomes the record of what the team did about it, not just the record that it fired.

See Real-Time Alerts & Evidence
Sover on desktop and mobile showing a shared alert channel: an IREX bot has posted a weapon-detection frame with the camera, the location and the case notes, and responders have replied underneath with voice notes and status updates
Illustrative mockup. The names, faces, address and match figure in it were invented for the mockup — it is not an incident record and not a measure of accuracy.

Share Evidence Media, Video and Photo, Securely

Sover’s file service takes the photo, video and voice notes a responder captures on the device in their hand, stores them on S3-compatible object storage, previews them in the app, and gives every file the permissions of the chat or workspace it was posted to. Payloads carry application-layer encryption on top of TLS, with a per-file key that is never stored on the server, so what sits on disk is the encrypted file and nothing else. Upload the same material to IREX and the modules that run on a live camera run on it too, which puts it in the archive as searchable events rather than as an attachment somebody has to remember.

See Security & Compliance
A three-stage diagram: capture on a responder’s device, then Sover’s chat and file service, then upload into the IREX platform where the same AI modules make the material searchable beside camera events

Coordinate the Response among Team Members

An event often needs people who were never platform users: a specialist, a decision-maker, another agency’s duty officer. Add them as users and user groups and each group gets its own Sover workspace for direct messages, public and private chats, voice calls and video calls. The officer in the field, the analyst at a desk and the duty officer at home then work from the same alarm, the same snapshots and the same playback links, and answer in the same thread from whatever they have to hand — Windows, macOS, Linux, Android, iOS or a browser.

See Real-Time Crime Centers
A responder holding a phone showing a Sover critical-alerts channel, where the alarm notifier has posted a weapon-detection frame with the camera name, the weapon class, the timestamp and a playback link
A weapon-detection alert reaching a Sover channel, on IREX’s own campus cameras.

Search Video Data Directly from a Chat

Ask IREX runs as a bot inside Sover, so an officer states the investigation in plain language — or sends a photo — from the phone they are already holding. The agent interprets the intent, cross-references the watchlists that apply, runs the multi-step search through the IREX API, and answers with a short result plus a link that opens the same results in the workspace with the filters already applied. It reads only what the account is entitled to see, and where the underlying action requires a Case ID, that requirement holds for a request made from the messenger. Ask IREX is shipping in beta on selected instances.

See Video Search & Investigations
A diagram of a Sover chat exchange: an officer asks for red trucks near the Central crossroads yesterday afternoon, Ask IREX replies with a count and a link into the workspace, and three steps below show the agent interpreting the intent, searching through the IREX API, and opening the workspace with filters pre-set

Sign In to IREX and Sover from a Single Account

Link the two accounts once — Profile, then Linked account, then Account linked to Sover — and the IREX sign-in screen gains a Sign in with Sover option that authenticates with the messenger credentials. That is one identity to issue, one to revoke and one to audit across both products, on top of the multi-factor authentication each enforces in its own right: Sover requires 2FA enrollment of every user, through a TOTP authenticator app or an email one-time code, and its mobile clients add a local passcode that can use the device’s own biometrics.

Docs: Access Your Workspace
The IREX sign-in screen with a Sign in with Sover option below the Log in button
The option appears on the sign-in screen once the accounts are linked. Capture from the platform documentation.

Run Sover on the Same Private Cloud as IREX

Sover deploys on the IREX Private Cloud, the same bare-metal-to-Kubernetes product that runs the video platform: one installation on hardware you own, on an entirely open-source stack with no third-party proprietary components, operational on three servers and scaling linearly by adding nodes. So there is one boundary to defend, one stack to put through source review or escrow, one set of dashboards for the operations team, and one jurisdiction holding both your video and your communications. The infrastructure both run on installs fully air-gapped.

See the IREX Private Cloud
One dashed panel labelled IREX Private Cloud on Kubernetes, holding an IREX column of ingest, analytics, event bus and search index beside a Sover column of core API, file service, conferencing and back office, over a shared data layer of Cassandra, Kafka, Elasticsearch, Ceph and PostgreSQL

Facts

Deployment
Private cloud on IREX infrastructure, customer on-premises with customer-managed Kubernetes, or hybrid and federated.
Throughput
Over 1,000 messages per second, supporting hundreds of thousands of users.
Clients
Windows, macOS, Linux, Android, iOS, and web, plus a Microsoft Outlook plugin.
Licensing
Per user, annually or perpetually. Source-code licensing is available for sovereign customers.

FAQ

How is the end-to-end encryption implemented?

In layers. All client-to-server and inter-service traffic uses TLS 1.2 or higher; messages and files are encrypted at rest server-side; and payloads carry application-layer encryption with two schemes, a session key negotiated at login and a per-file key that is not stored on the server, so only the encrypted file resides there. Cross-server federation messages are encrypted end to end.

Can we run it entirely on our own infrastructure?

Yes, and for most sovereign customers that is the point. Sover deploys on-premises on customer-managed Kubernetes or in a private cloud, so data never leaves the network you control, which is what supports data-localization regimes.

Can we brand it as our own?

Yes. Sover is explicitly rebrandable and source-code licensable for sovereign governments and regulated organizations.

Does it work without IREX?

Yes. Sover is a standalone communications platform, licensed per user. Inside an IREX deployment it additionally acts as the secure front end for alerts and Ask IREX.

Replace the Consumer App in the Field

A Sover pilot runs three to nine months from first conversation to steady state, with real user cohorts on real devices.