Citizen Instances
Shared instances the operator runs for residents and small businesses, with registration that follows the operator’s own account policies.
Official channels, service assistants and AI agents that citizens reach in the messenger they use every day, published under your organization’s name and symbols and hosted on servers in your country.
Overview
A resident who pays a tax, renews a registration and books an appointment often meets a different website, app and sign-in for each one, while the conversations of daily life happen elsewhere, on messengers the state does not run.
With Sover, a national operator or a city runs its own messenger and builds public services into it: official channels for news and alerts, service assistants on the Bot API, and AI agents under the operator’s security policy. Each service is designed and connected by the operator; Sover provides the platform it runs on.
Your Brand
Sover is rebrandable. The app citizens install can carry the name, symbol and colors of the ministry, city or national operator responsible for it, and be released under that organization’s name. Citizens see their state, not a vendor.
Your name and symbol. App name, icon, colors and welcome screen in the identity of the responsible organization.
Published on your behalf. Apps for Android, iOS, Windows, macOS, Linux and the web, with mobile distribution through Google Play, the Apple App Store and Huawei AppGallery.
Your language. Interface localization in more than 20 languages.
Agreed for your project. The branding scope, application distribution and delivery responsibilities are set in the agreement; source-code licensing is available.
Why Sover
Citizens reach the state through separate service apps and portals, and talk to each other on public messengers. Sover puts official services into a messenger the state itself runs.
| Separate Service Apps and Portals | Public Messengers | Sover | |
|---|---|---|---|
| Where Citizens Find Services | One app or website for each agency or service. | Beside personal chats, inside the provider’s app. | Official channels and service assistants in one messenger, beside citizens’ own chats. |
| Whose Name Is on the App | Each agency’s own, different from one service to the next. | The provider’s name and brand. | The responsible organization’s: its name, symbol and colors, in apps released under its name. Custom Branding |
| Where the Conversations Are Stored | In each service’s own systems. | On the provider’s servers, in the locations the provider chooses. | On servers in your country: your data center, or a trusted in-country provider’s. |
| Who Sets the Rules | Each service, separately. | The provider, for all its users. | Your administrators: who can register, two-factor authentication, roles, and what crosses to other instances. |
| How a New Service Is Added | A new app, site or portal page. | Within the provider’s bot and integration terms. | A bot on the Bot API with 50+ REST methods, or an AI agent through MCP or REST, connected to your existing systems. |
Compared by category of service; individual apps, portals and messengers differ, so evaluate each against your requirements.
Use Cases
Broadcast channels for city news, public notices and emergency information, with comments on or off as the channel owner decides.
Bots on the Bot API answer requests, offer buttons for the next step and send confirmations, connected to the systems behind each service.
Agents connect through MCP or REST and answer citizens within the permissions the operator grants, under one security policy.
The app carries the name, symbol and colors of the responsible organization and is released under its name.
Shared instances the operator runs for citizens can connect to agency instances under each side’s federation policy.
The whole platform runs on servers in your country, operated by your team or a trusted local provider.
Illustrative chats in a fictional Miraflores city app, published under the city’s own name and symbol. Services shown are examples an operator could build on Sover, not built-in Sover services.
Miraflores app and lighthouse symbol: an illustrative brand, not an official municipal app or emblem.
Deployment
In a national federation, for example, the operator runs shared, multi-tenant instances for citizens and small businesses, while ministries and city governments run dedicated instances and security agencies run high-security ones. Each instance controls what crosses to the others.
Every instance runs on infrastructure in your country: bare metal with the Sover Private Cloud included, your Kubernetes cluster, or your virtual machines. This is an operator-run service, not a public cloud subscription.
Shared instances the operator runs for residents and small businesses, with registration that follows the operator’s own account policies.
Ministries, cities and agencies keep their own instances and publish their channels and assistants to citizens through the federation they approve.
Federated NetworkThree deployment options in one model, run by your team or a trusted in-country provider.
Deployment OptionsIncluded
Channels and chats. Broadcast channels, group chats and direct messages with files, photos, voice and video.
The Bot API. 50+ REST methods and a Python client library for building service assistants.
AI agents. MCP and REST interfaces for agents that act within your security policy.
Your brand. Rebrandable apps for Android, iOS, Windows, macOS, Linux and the web, in more than 20 interface languages.
Your rules. Mandatory two-factor authentication, role-based access, audit logging and per-instance federation policy.
Your hosting. Three deployment options in one model, with the Sover Private Cloud included.
Services are built, not built in. Tax, permit, benefit, payment and identity services need their own service design and integrations with the systems behind them; they are not Sover features.
Channels carry no buttons. Bot messages with buttons work in chats with the assistant, not in information channels.
Branding is agreed. The branding scope, store publishing and delivery responsibilities are set for each project.
Mobile push uses platform services. Push notifications to phones are delivered through the Apple, Google or Huawei notification services.
Hosting is not compliance. Sover’s controls support your compliance program; your organization assesses each service 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.
One Platform
The deployment that carries citizen services can extend, on the same platform or through federated instances, to the applications below.
Messaging, meetings and AI agents for ministries and agencies, hosted in your country.
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 which services you plan to offer citizens and we will arrange a briefing for your team.
Sover can be part of an operator-run communication service. Functions such as payments, e-wallets, or commerce need their own service design and integrations; they should not be assumed to be built-in Sover capabilities.
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.
Sover runs on Android, iOS, Windows, macOS, Linux, and web browsers, and its mobile apps are distributed through Google Play, the Apple App Store, and Huawei AppGallery. For a rebranded app, the store listings, the publishing organization, and the distribution work are agreed for the project.
An operator can design a service around shared instances connected to other instances under its policies. This is an operator-run deployment model, not a promise that Sover itself is a public cloud service.
Sover provides a Bot API for building integrations that bring messages and actions into the communication environment. Scope each integration around the source system, target conversations, permitted actions, and deployment requirements.
Yes. Sover supports MCP and chatbot APIs for AI-agent participation under the customer's security policy. The permitted actions and deployment scope should be agreed explicitly, including any access to history or participation in conferences.
Sover offers source-code licensing and rebranding, but their scope and commercial terms must be agreed. Ask the proposal to identify the rights, deliverables, maintenance responsibilities, and any application-distribution work included.
Yes. Sover supports interface localization in more than 20 languages. Confirm the languages and client versions required by your users during deployment planning.