On-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
Messaging, video meetings and AI agents for ministries and agencies, on servers in your country, run by your own team or a trusted local provider, under a security policy you set.
From one confidential government deployment, which we do not name.
Overview
Ministries, agencies and city governments coordinate every day in chats and calls. When that happens on a public messenger or on a platform hosted abroad, the messages, files and contact lists of government sit on infrastructure the state does not operate, under terms it did not write.
Sover is a sovereign communications platform that a government runs itself: messaging, voice and video meetings, workspaces, bots and AI agents, on servers in your country, under your own security policy. Agencies that keep separate instances work together through federation, each controlling its own.
Why Sover
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 government runs.
| Public Messengers | Managed Enterprise Platforms | Sover | |
|---|---|---|---|
| All Data in Your Country | 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 in your country: your data center, or a trusted in-country provider’s. |
| Full Control of the Technology Stack | The provider runs and changes the service for all its users. | The provider operates and updates the platform for all its customers. | Your team or your provider runs the whole stack, on bare metal with the Sover Private Cloud included, on your Kubernetes cluster or on your virtual machines. The source code can be licensed. |
| 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 certificate trust store you control; payload encryption configured 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, the Bot API with 50+ REST methods, MCP for AI agents and one-way sync from Microsoft Active Directory. |
| 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
Direct messages, group chats and broadcast channels for staff, in workspaces that keep departments apart on one deployment.
Agencies that run separate instances work together through closed federation, each approving its partners and limiting what crosses.
Video meetings with screen sharing from web and desktop, and call transcription and summaries from the AI assistant.
Agents connect through MCP and chatbot APIs, act for users within the security policy, review message history and join video meetings.
Bots post events from your systems into the chats where staff respond. With IREX, alarm notifications arrive in dedicated security spaces.
A back-office console for users, roles, devices and sessions, with administrative audit logging and one-way sync from Microsoft Active Directory.
Illustrative Scenario
An illustrative city workspace: field teams, citizen alerts and the council work in one app, and the morning operations sync runs as a video meeting, all on servers the city controls.
Patrol teams, citizen alerts and the city assistant share one workspace, and an official switches between workspaces in one tap.
Department heads join the operations sync, and the service plan is shared on screen from the desktop app.
Illustrative workspaces, people and messages. Not a customer reference.
Deployment
Sover runs where your government decides: in your own data center, or with a trusted in-country provider, such as a local system integrator or a private-cloud operator you select. The hosting operator, isolation and region are agreed for each project.
In a national federation, for example, ministries and city governments run dedicated instances, while defense, intelligence and national police run high-security instances of their own. Each opens only the exchanges it approves.
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 OptionsSover on a Kubernetes cluster your team already operates. The Sover Private Cloud stays included; this setup takes a custom SLA.
Sover on the virtual machines you already run, including legacy hypervisors such as VMware ESXi.
Included
Your hosting. 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 brand. Rebrandable apps for Windows, macOS, Linux, Android, iOS and the web; source-code licensing by agreement.
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.
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 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.
Federated data reaches partners. What you exchange through federation can be stored on the participating instances; the federation design sets what crosses.
Your own cluster, a custom SLA. On a Kubernetes cluster your team operates, support for the cluster stays with you and the SLA is agreed for the setup.
No uptime figure. Sover is hosted by you, so the SLA sets support response times, not availability.
Beyond One Ministry
The deployment that serves one ministry can extend, on the same platform or through federated instances, to the applications below.
Official channels and service bots a national operator builds on the Bot API, which citizens reach in the messenger they already use.
Learn MoreShared instances a national operator runs on its own infrastructure for citizens and small businesses.
Learn MoreA national police force can run a high-security instance of its own and open only the exchanges it approves.
Learn MoreBroadcast channels and operational bot notifications for the teams that respond, with IREX alarm notifications where IREX runs.
Learn MoreRegulated institutions keep communications on infrastructure they operate, with role-based access and audit logging.
Learn MoreMessaging and video meetings for clinical and administrative teams, hosted where the organization decides.
Learn MoreSeparately hosted operators keep their own instances and connect them where they need controlled communication.
Learn MoreTell us about your agency and we will arrange a briefing for your team.
Agencies can use Sover for internal messaging and meetings on infrastructure selected for their requirements. Where agencies operate separate instances, federation can support cross-agency collaboration under agreed partner and access policies.
It means your organization can host and operate its communications environment under its own policies. Hosting location, access controls, deployment configuration, and connected services must be selected together to meet your data-control requirements.
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.
Start with where your data will be hosted, who operates the service, how separate organizations collaborate, and what branding or source-code rights you need. Then test the messaging, meeting, security, and integration workflows required by your users.
Federation is useful when organizations need to operate independently but still communicate. A single deployment with workspaces may suit internal teams; independently hosted organizations should evaluate federation and the policies governing information exchange.
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.
Yes. Sover is rebrandable, so an organization can discuss a deployment under its own identity. The branding scope, application distribution, and delivery responsibilities are agreed for the project.
Standard Support is included in the subscription or license, in accordance with the agreement: online tickets, email and messenger support, business-day coverage, and 24×5 weekday coverage, with initial response from four hours for urgent issues. Premier Support is available for an additional fee and adds 24×7 deployment health monitoring, one-hour and two-hour initial response for urgent and high-impact issues, weekend coverage for those escalations, and a senior support team. The full terms are in the Sover SLA.