Staff MessengerOn-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
Communications for Healthcare Teams
Messaging, video meetings, bots and AI agents for hospitals and health services, on servers you control, run by your own team or a trusted local provider, under a security policy you set.
- 3
- Deployment Options in One Model
- 6
- Client Platforms, Phone to Web
- 20+
- Interface Languages
Overview
Hospitals Run on Conversations
Every shift, a hospital coordinates beds, rotas, deliveries, repairs and appointments in chats and calls. When that work moves to personal phones and public messenger groups, the conversations of the organization sit on infrastructure it does not operate, outside its own accounts, access rules and audit.
Sover is a sovereign communications platform that a health organization runs itself: messaging, voice and video meetings, workspaces, bots and AI agents, on servers you control, under your own security policy. Patient records stay in your clinical systems; Sover carries the coordination around them.
Why Sover
Different from Public Messengers and Managed Platforms
Public messengers, such as WhatsApp and Telegram, and managed enterprise platforms, such as Microsoft Teams and Slack, are services their providers host and run. Sover is software your health organization runs.
| Public Messengers | Managed Enterprise Platforms | Sover | |
|---|---|---|---|
| Staff 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 you choose: your data center, or a trusted provider’s in your country. |
| Accounts the Organization Controls | Personal accounts on personal phones, created and kept by each user. | Organization accounts, administered within the provider’s service. | Accounts on your own deployment: administrators add and remove staff, with one-way sync from Microsoft Active Directory. |
| Your Security Policy and Encryption | 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; TLS 1.2 or higher with a trust store you control; payload encryption per deployment; and end-to-end encrypted secret chats. |
| Your Brand and Your Integrations | The provider’s app, brand and integration terms. | The provider’s app, extended through its own marketplace and APIs. | Apps rebranded under your name, and the Bot API with 50+ REST methods and MCP, so your own rota, booking and facilities systems can post into the chats where staff work. |
| 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. WhatsApp, Telegram, Microsoft Teams and Slack are trademarks of their respective owners.
Use Cases
One Platform for the People Who Keep a Hospital Running
- Messaging & Channels
Ward and Department Messaging
Group chats for wards and departments, direct messages between colleagues, voice messages, photos and files, in workspaces that keep teams apart on one deployment.
- Video Conferencing
Huddles and Planning Meetings
Video meetings for staff, with screen sharing from web and desktop, and call transcription and summaries from the AI assistant for review afterward.
- Integrations & APIs
Rota, Reminder and Facilities Bots
Bots you build on the Bot API post open shifts, appointment-reminder summaries and estates updates into the chats where staff respond. Your systems stay the record.
- Federated Network
Suppliers and Partner Organizations
Separately hosted organizations, such as a supplier or a neighboring health service, work with you through closed federation, each approving its partners.
- Security & Compliance
Sensitive Conversations
Mandatory two-factor authentication, role-based access and administrative audit logging, with end-to-end encrypted secret chats for private conversations.
- AI Agents & Assistants
AI Agents under Your Policy
Agents summarize chats, schedule meetings and post channel news, acting for users only within the security policy that governs everyone.
A Day at a Hospital Trust, in One App
Illustrative chats at a fictional NHS hospital trust. Bots and services shown are examples a health organization could build on the Sover Bot API.
An illustration of how a health service such as the NHS could use Sover. The NHS is not a Sover customer and has not endorsed Sover. The NHS name and logo are trademarks of their owners and are shown for illustration only. The trust, people and messages are fictional.
Scenarios
The Scenarios in Detail
Each conversation in the demo stands for work a health organization can run on Sover. Bots and services are what your team or partner builds on the platform; the people and the trust are fictional.
-
The Morning Operations Huddle
Operations managers and directors
- The Situation
- Before the day starts, leaders need the same picture of beds, discharges and pressure points, and a quick decision.
- On Sover
- A site-report bot posts the 08:00 summary into the leadership group. The team meets by video for fifteen minutes, and the AI assistant’s summary arrives in the chat for review.
- Built With
- Group chats, video meetings, AI assistant summaries, a bot on the Bot API
-
Covering a Shift Gap
Ward managers and the staffing team
- The Situation
- Two staff call in sick for a weekend shift, and the ward needs cover without a round of phone calls.
- On Sover
- The manager asks a rota bot to offer the shifts to staff with the right skills. Replies come back to the bot, and the updated rota lands in the ward group.
- Built With
- A bot on the Bot API connected to your rota system, group chats, files
-
Planning with a Consultant
Consultants and operations staff
- The Situation
- A consultant needs a clinic room for a new colleague and time to go through the ward’s winter plan.
- On Sover
- They agree the room in a direct chat, a voice message fills in the detail, and an 18-minute video call settles the plan.
- Built With
- Direct messages, voice messages, one-to-one video calls
-
Appointment Reminders and Freed Slots
Outpatient administrators
- The Situation
- Patients who cannot attend leave clinic slots empty unless someone notices in time to offer them again.
- On Sover
- A reminder service the trust builds reports the day’s reschedule requests to administrators, who release the freed slots to the waiting list with one tap.
- Built With
- A service built on the Bot API, connected to your booking system; your branded app for patients
-
Working with a Supplier
Procurement and supply staff
- The Situation
- A delivery of consumables has to move by a day, and the loading bay needs the new note.
- On Sover
- The supplier’s account manager, on her organization’s own instance, answers in a federated chat and sends the updated delivery note and a photo on arrival.
- Built With
- Closed federation between separately hosted organizations, files and photos
-
Briefing Every Member of Staff
Communications teams and executives
- The Situation
- Vaccination clinics, winter messages and policy changes have to reach every member of staff, not only those on email.
- On Sover
- A read-only staff channel carries the notice and the chief executive’s video message to every device, while estates and wards keep their own groups for local updates.
- Built With
- Broadcast channels, video messages, group chats with photos and voice messages
Deployment
Hosted Where Your Organization Decides
Sover runs in your own data center or with a trusted provider in your country, such as a local system integrator or a private-cloud operator you select. The hosting operator, isolation and region are agreed for each project.
A health system can run one deployment with a workspace for each hospital or service, or let separately hosted organizations keep their own instances and connect them through federation, each opening only the exchanges it approves.
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 hosting. Three deployment options in one model, with the Sover Private Cloud included.
-
Your staff directory. Administrators manage users, roles, devices and sessions, with one-way sync from Microsoft Active Directory.
-
Your policy. Mandatory two-factor authentication, role-based access 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 apps. Rebrandable apps for Windows, macOS, Linux, Android, iOS and the web, in 20+ interface languages.
-
Your support. Standard Support under the Sover SLA, with Premier Support available.
Stated Limits
-
Not a clinical system. Sover carries staff coordination. Patient records, clinical decisions and bookings stay in the systems that hold them; bots can post notices from those systems.
-
Video is for your accounts. Video meetings connect people with accounts on your deployment. Talk to us before planning patient consultations.
-
Hosting is not compliance. Sover’s controls support your compliance program; your organization assesses configuration, access, integrations and procedures against its obligations.
-
End-to-end means secret chats. Standard chats use transit, at-rest and payload encryption; the end-to-end claim covers secret chats.
-
Bots are built for you. Rota, reminder and facilities bots are integrations scoped per project on the Bot API, not ready-made products.
-
Mobile push uses platform services. Push notifications to phones are delivered through the Apple, Google or Huawei notification services.
Beyond One Hospital
The Same Platform Serves the Wider Public Sector
The deployment that serves one health organization can extend, on the same platform or through federated instances, to the applications below.
Government Agencies
Ministries and agencies on their own instances, working together through federation under each one’s policy.
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 MoreLaw Enforcement
A national police force can run a high-security instance of its own and open only the exchanges it approves.
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 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 organization and we will arrange a briefing for your team.
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 Sover support voice and video calls?
Yes. Sover supports one-to-one audio and video calls, group audio calls, and video conferences, bringing live discussion into the same environment as team messaging.
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.
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.
Can Sover transcribe calls and summarize conversations?
Yes. Sover's AI assistant supports voice-call transcription and conversation summaries. Confirm availability and access in your deployment, and review generated output before relying on it as a record of decisions.
Can meetings be recorded?
Recording is available subject to the deployment configuration and client. Agree who may record, where recordings are stored, and how long they are retained before using recording for sensitive or regulated conversations.
Can different departments have different workspace members?
Yes. Workspaces have their own membership and roles, allowing teams to organize their conversations separately. A workspace is a collaboration boundary; it should not be treated as proof of a separately hosted or isolated tenant.
Do we have to move our communications to a public cloud?
No. Sover is user-hosted: it runs on infrastructure your organization controls, whether your own servers with the Sover Private Cloud, your Kubernetes cluster, or your virtual machines, so the hosting environment can be selected for your organization's requirements.