Oceanside Police
Camera 3 · 01:4201:42On-Premises
Bare metal in your data center, with the Sover Private Cloud included: provisioning, storage, data services, observability, security and a management console in one product.
Deployment Options
Law Enforcement Communications on an Instance You Control
Real-time alerts, shared case material and coordinated response for police departments, in a messenger your agency hosts, under a security policy you set.
Overview
Police Conversations Belong on Police Infrastructure
Officers coordinate calls, share scene photos and brief detectives in chats every shift. When those chats run on a consumer messenger or a platform hosted elsewhere, case material and contact lists sit on infrastructure the department does not operate, and alarms from its own systems arrive somewhere else.
Sover is a sovereign communications platform a department runs itself: messaging, voice and video calls, broadcast channels and bots, on servers it controls, under its own security policy. With the IREX Ethical AI Platform, IREX alarm notifications arrive in the same app, beside the chats where officers respond.
Why Sover
Different from Consumer Messengers and Managed Platforms
Consumer messengers and managed enterprise platforms are services their providers host and run. Sover is software your department runs.
| Consumer Messengers | Managed Enterprise Platforms | Sover | |
|---|---|---|---|
| Case Conversations on Your Servers | Stored on the provider’s servers, in the locations the provider chooses. | Stored in the provider’s cloud, in the regions the provider offers. | Stored and processed on servers your agency controls: your data center, or a trusted provider you select. |
| An Instance of Your Own | One service shared with every other user. | A tenant on the provider’s platform. | Your own instance. Through closed federation, it exchanges messages and calls only with the agencies you approve, and you limit what crosses. |
| Your Security Policy | One policy for every user, set by the provider. | Settings within the options the provider offers. | Your administrators set two-factor enrollment, roles, devices and sessions, with administrative audit logging and end-to-end encrypted secret chats. |
| Alerts from Your Own Systems | Integrations on the provider’s terms. | The provider’s marketplace and APIs. | The Bot API with 50+ REST methods posts events from your systems into chats, and IREX alarm notifications arrive in dedicated security spaces where you run the IREX platform. |
| A Support Commitment to Your Installation | General terms of service, written for every user. | The provider’s standard service terms, the same for every customer. | The Sover SLA for your installation: Standard Support included, and Premier Support with 24×7 deployment health monitoring and one-hour initial response for urgent issues. Service Level Agreement |
Compared by category of service; individual services, plans and settings differ, so evaluate each against your requirements.
Use Cases
From the Alarm to the Report, in One App
- Sover with IREX
Real-Time IREX Alarms
With the IREX platform, IREX alarm notifications arrive in real time in dedicated security spaces, where officers on duty see the event and discuss it.
- Messaging & Channels
Ask IREX and Evidence Sharing
Ask IREX, shipping in beta on selected instances, searches the IREX archive from a chat. Officers share photos, video, voice messages and files with detectives in a case chat.
- Video Conferencing
Response Coordination
A group chat for the units on a call, a broadcast channel for dispatch updates, and voice calls or video meetings when a shift needs to talk.
- AI Agents & Assistants
Bots from Your Own Systems
Bots post events from the systems you connect into the chats where officers act, and AI agents work under the same security policy.
- Federated Network
A High-Security Instance
A police force can run an instance of its own and, through closed federation, work only with the agencies it approves.
- Security & Compliance
Access, Devices and Audit
Mandatory two-factor authentication, role-based access, device and session management, administrative audit logging and end-to-end encrypted secret chats.
Sover with IREX
IREX Alarms and Ask IREX, Where Officers Already Talk
Sover connects to the IREX Ethical AI Platform. IREX alarm notifications arrive in real time in dedicated security spaces, where the officers on duty see the event and discuss it in context.
Ask IREX, shipping in beta on selected instances, lets users search the IREX archive for people, vehicles and events in natural language from a Sover chat. IREX agentic AI runs each request under the IREX platform’s Case ID and audit-logging controls.
Both require the IREX platform; neither is standalone video analytics in Sover.
One Night Shift, in One Messenger
Illustrative chats from a fictional night shift. Bots are integrations a department could build. IREX features require the IREX platform; Ask IREX is shipping in beta on selected instances.
Oceanside Police branding, people and events are fictional and illustrative. The City of Oceanside and its police department are not Sover customers, and the emblem is not their seal.
Deployment
Your Instance, on Infrastructure You Control
Sover runs where your agency decides: in your own data center, or with a trusted provider you select. The hosting operator, isolation and region are agreed for each project.
In a national federation, for example, national police can run a high-security instance of their own, while city governments run dedicated instances. Each opens only the exchanges it approves, and each controls what crosses, such as allowing messages and calls while disabling forwarding or contact sharing.
Your Kubernetes Cluster
Sover on a Kubernetes cluster your team already operates. The Sover Private Cloud stays included; this setup takes a custom SLA.
Your Virtual Machines
Sover on the virtual machines you already run, including legacy hypervisors such as VMware ESXi.
Included
What Is Included, and Where the Limits Are
Included
-
Your instance. Three deployment options in one model, with the Sover Private Cloud included.
-
Your policy. Mandatory two-factor authentication, role-based access, device and session management, and administrative audit logging.
-
Your encryption setup. TLS 1.2 or higher with your own trust store, encryption at rest, session-key and file-key payload encryption, and end-to-end encrypted secret chats.
-
Your integrations. The Bot API with 50+ REST methods and a Python client library, and MCP for AI agents.
-
Your partners. Open or closed federation with the agencies you approve, under per-user and per-group policies.
-
Your support. Standard Support under the Sover SLA, with Premier Support available.
Stated Limits
-
IREX features need IREX. Alarm notifications and Ask IREX require the IREX platform, and Ask IREX is shipping in beta on selected instances.
-
A chat is not an evidence system. Officers share and discuss material in chats; keep originals in your evidence system, as your procedures require. Audit logging alone is not a forensic or legal-hold system.
-
An alert is not incident management. A bot or IREX notification brings an event into a chat for review and discussion; it does not by itself create an incident-management system.
-
End-to-end means secret chats. Standard chats use transit, at-rest and payload encryption; the end-to-end claim covers secret chats.
-
Mobile push uses platform services. Push notifications to phones are delivered through the Apple, Google or Huawei notification services. Review each external dependency when you design a restricted network.
-
Hosting is not compliance. Sover’s controls support your compliance program; your agency assesses configuration, access, integrations and procedures against its obligations.
Beyond One Department
The Same Platform Serves the Agencies You Work With
The instance that serves one department can extend, on the same platform or through federated instances, to the applications below.
Government Agencies
Ministries, agencies and city governments on instances they control, working together through federation.
Learn MoreE-Government Services
Official channels and service bots a national operator builds on the Bot API, which citizens reach in the messenger they already use.
Learn MoreSovereign Social Media
Shared instances a national operator runs on its own infrastructure for citizens and small businesses.
Learn MoreFirst Responders & Alerts
Broadcast channels and operational bot notifications for the teams that respond, with IREX alarm notifications where IREX runs.
Learn MoreFinancial Services
Regulated institutions keep communications on infrastructure they operate, with role-based access and audit logging.
Learn MoreHealthcare
Messaging and video meetings for clinical and administrative teams, hosted where the organization decides.
Learn MoreCritical Infrastructure
Separately hosted operators keep their own instances and connect them where they need controlled communication.
Learn MoreQuestions, or Ready for a Briefing?
Contact Sales
Tell us about your department and we will arrange a briefing for your team.
How can a police department use Sover?
A department can run Sover on infrastructure it controls for officer messaging, group chats, broadcast channels, and voice and video calls, and connect its own systems through bots. With the IREX platform, IREX alarm notifications arrive in Sover. Agencies that run separate instances can work together through federation under agreed partner policies.
Does Sover work with IREX?
Yes, with the IREX Ethical AI Platform. IREX alarm notifications arrive in real time in dedicated security spaces in Sover, and Ask IREX, shipping in beta on selected instances, lets users search the IREX archive for people, vehicles and events from a Sover chat, under the IREX platform’s Case ID and audit-logging controls. Both require the IREX platform; neither is standalone video analytics in Sover. Sover and IREX are related parties. They share one team, and Sover is majority-owned by IREX co-founder Nik Ptitsyn.
Can officers share photos, video and files in a case chat?
Yes. Sover supports file and media sharing, including images, videos, voice messages and documents, with in-app previews for supported formats. Upload limits and preview behavior depend on the deployment and client. A chat supports coordination; keep originals in your evidence system, as your procedures require.
Can Sover support operational notifications?
Yes. A bot integration can bring a system event into an authorized conversation where staff can review and discuss it. Scope the source system, destination, permissions, and expected response; the message does not by itself create an incident-management system.
Can we choose which organizations our instance communicates with?
Sover supports open and closed federation, including approved-partner policies. Define the intended partners and permitted communication when designing the deployment, then validate the required restrictions on the selected release.
Does Sover provide administrative audit logging?
Yes. Administrative audit logging is part of Sover's control set. Agree the events you need to record and the access, retention, and export requirements; audit logging alone does not establish a complete forensic or legal-hold system.
Does Sover offer end-to-end encryption?
Yes. Sover offers end-to-end encrypted secret chats for sensitive private conversations. Standard chats have a different security model, including transport, at-rest, and payload-encryption controls; the secret-chat claim should not be extended to every conversation or integration.
Does hosting Sover on-premises automatically meet our compliance obligations?
No. Hosting is one part of a compliance program. Your organization must assess configuration, access, integrations, devices, data flows, and operating procedures against its obligations. Sover's controls can support that work; hosting alone does not establish compliance.
Does on-premises deployment mean there are no external dependencies?
Not automatically. Push services, identity providers, calendar systems, AI services, and other integrations can introduce external dependencies. Review the actual data flows and enabled services when designing a restricted-network deployment.