Quetzal EnergíaOn-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
Critical Infrastructure Communications on Servers You Control
Messaging, video meetings, operational bots and company channels for control rooms, field crews and maintenance teams in energy, utilities and transport, hosted by your organization under your own security policy.
- 3
- Deployment Options in One Model
- 50+
- REST Methods in the Bot API
- 20+
- Interface Languages
Overview
Operational Conversations Belong on Your Own Infrastructure
Grid operators, water and gas utilities and transport networks run on coordination: control-room shifts, field crews, maintenance teams, contractors and storm bridges. When that coordination happens in consumer messengers, photos of substations, switching orders, staff lists and network details end up on services the operator does not run.
Sover is a communications platform an operator hosts itself: messaging, voice and video meetings, broadcast channels, bots and AI agents, under the operator’s own security policy. Alarms and tickets from your own systems reach the chats where staff respond, through the Bot API.
Why Sover
Different from Public Messengers and Managed Platforms
Public messengers and managed enterprise platforms are services their providers host and run. Sover is software your organization runs, next to the systems it already operates.
| Public Messengers | Managed Enterprise Platforms | Sover | |
|---|---|---|---|
| Hosted Where You Decide | On the provider’s servers, in the locations the provider chooses. | In the provider’s cloud, in the regions the provider offers. | In your data center or with a trusted provider you select: bare metal with the Sover Private Cloud included, your Kubernetes cluster or your virtual machines. |
| Your Staff, Your Contractors, Your Rules | Open sign-up, with contact and group rules set by the provider. | Accounts and guest access within the provider’s options. | Access follows your registration policy. Contractors on their own instances connect through federation, under the partner and access policies you approve. |
| Your Security Policy | One policy for every user, set by the provider. | Settings within the options the provider offers. | Mandatory two-factor authentication, role-based access, device and session management and audit logging; TLS 1.2 or higher with your own trust store; end-to-end encrypted secret chats. |
| Your Systems in the Conversation | Integrations on the provider’s terms. | The provider’s marketplace and APIs. | Alarm, ticket and roster bots you build on the Bot API, with 50+ REST methods and a Python client, and MCP for AI agents. |
| 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 Control Room to the Last Tower
- Messaging & Channels
Shift, Crew and Maintenance Chats
Group chats for each control-room shift, line crew and substation team, with photos, video, voice messages and documents shared from the field.
- Integrations & APIs
Alarms and Tickets in Context
Bots you build on the Bot API post events from your SCADA, ticketing or roster systems into the chat where staff respond, and mention the person on duty.
- Video Conferencing
Storm and Incident Bridges
Video meetings for response bridges, with screen sharing from web and desktop, and call transcription and summaries from the AI assistant.
- Federated Network
Contractors and Partner Operators
Organizations on separate instances communicate through federation, each approving its partners and limiting what crosses, such as forwarding or contact sharing.
- AI Agents & Assistants
AI Agents for Operations
Agents connect through MCP and chatbot APIs, summarize chats, post channel news and act for users within the security policy.
- Administration
Access and Audit
A back-office console for users, roles, devices and sessions, administrative audit logging and one-way sync from Microsoft Active Directory.
One Hurricane Night at a Grid Operator
Illustrative chats at a fictional Mexican grid operator. The alarm, ticket and roster bots are integrations an operator builds with the Bot API.
Quetzal Energía, its people, substations, storm and events are fictional and illustrative. Not a customer reference.
Deployment
On Your Network, Next to Your Operational Systems
Sover runs where your organization decides: in your own data center, or with a trusted provider you select. The hosting operator, isolation and region are agreed for each project.
Inside one deployment, workspaces keep the control room, regions and maintenance teams apart. Where a generation company, a network operator or a contractor runs its own instance, for example, federation connects them under the policies each one sets.
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 teams. Direct messages, group chats, broadcast channels and workspaces, with files, photos, video and voice messages.
-
Your systems. The Bot API with 50+ REST methods, a Python client and server-sent events, and MCP for AI agents.
-
Your policy. Mandatory two-factor authentication, role-based access, device and session management, and administrative audit logging.
-
Your partners. Open or closed federation with the organizations you approve, under per-user and per-group policies.
-
Your support. Standard Support under the Sover SLA, with Premier Support available.
Stated Limits
-
Bots are integrations you build. An alarm or ticket bot brings an event into a chat; it does not replace your SCADA, outage management or incident process.
-
Restricted networks need design. Mobile push travels through the Apple, Google or Huawei notification services, and identity, calendar and AI integrations can add dependencies. Review the data flows for your 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.
-
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. High availability and recovery are designed and tested for each installation.
Other Industries
The Same Platform across the Public Sector
The deployment that serves one operator can connect, through federation, to the agencies and services it works with.
Government Agencies
Ministries and agencies on their own instances, working together through closed 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 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.
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 MoreQuestions, or Ready for a Briefing?
Contact Sales
Tell us about your operation and we will arrange a briefing for your team.
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.
What can a Sover bot be used for?
A bot can deliver operational messages into an authorized conversation, helping a team review an event and discuss it in context. The available actions depend on the bot's permissions and the integration; a notification alone is not a complete incident-management workflow.
How can a distributed enterprise use Sover?
Departments and projects can organize their discussions in workspaces, groups, and announcement channels. If separate organizations need independent deployments, federation is a separate design choice for communication between them.
Can I share documents and media in a conversation?
Yes. Sover supports file and media sharing with in-app previews for supported formats. Upload limits and preview behavior depend on the deployment and client, so check large-file and specialist-format requirements during evaluation.
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.
Can anyone register for our organization's Sover environment?
Access follows the organization's registration and account policies. The application FAQ describes registration for employees of authorized organizations, so downloading the application alone does not grant access to an organization's environment.
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.
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.
Can the system be designed for high availability?
High availability is a deployment-design requirement covering application services, databases, storage, media, and dependencies. The architecture and acceptance tests must establish the workload sustained during failures rather than relying on a universal replica count.
How are backups and disaster recovery planned?
Agree what must be backed up, how long backups are retained, where they are kept, and how recovery will be tested. Include configuration, files, recordings, and databases. Recovery-time and recovery-point objectives are agreed for the proposed installation.