Scope and Hosting
The user scope, the hosting model, the required features and the integrations the proposal covers.
Three ways to license, one conversation about scope. Sover runs on infrastructure you own, with the Sover Private Cloud and Standard Support included, and every proposal is written for your users, deployment and integrations rather than taken from a price list.
Choose a Model
Sover is user-hosted, on your own bare metal with the Sover Private Cloud, on your Kubernetes cluster or on your virtual machines, and is not offered as public multi-tenant SaaS. The customer selects the deployment option and operating responsibilities during solution design.
There is no public price list. Define your user scope, hosting model, required features, integrations and support responsibilities, then request a proposal for that scope.
Licensed per user, per year.
Support Standard Support included; Premier Support available.
SKU SOVER-MESSENGER-1Y
Licensed per user, with three years of support included.
Support Extended with SOVER-MESSENGER-EXT.
SKU SOVER-MESSENGER-PERP
The source code can be licensed, and the apps rebranded under your own name. The license scope, permitted changes, maintenance responsibilities and delivery terms are set in the agreement.
Custom BrandingIncluded and Available
Each license comes with the platform to run Sover on and a service level agreement. Choose the support package your installation needs.
A turnkey platform for your own bare metal or virtual machines: orchestration, storage, data services, monitoring and a management console.
Deployment OptionsIncluded
Online tickets, email and messenger support, business-day and 24×5 weekday coverage, with initial response from four hours on urgent issues.
Standard SupportIncluded
24×7 deployment health monitoring, initial response in one hour on urgent issues and two hours on high-impact ones, weekend coverage and a senior support team.
Premier SupportAvailable
The Process
There is no generic rollout duration. The schedule depends on infrastructure readiness, security review, integration work, client distribution and acceptance requirements, and it is planned once those are scoped.
Your user scope, the hosting model, the features you need, the integrations and who is responsible for support. This is what a proposal is written against.
A session built on scenarios close to yours, shown on a build that has been checked and rehearsed first, with fictitious organizations and data rather than customer references.
Book a DemoSizing discovery records your workload: people and sessions, messaging, calls and meetings, storage and retention, AI features, resilience and network. It remains an estimate until measured evidence supports a decision for your deployment.
A proposal for that scope, then an agreement that identifies the contracting party and the responsibilities for the deployment, with support and service levels set in the statement of work.
The project plan follows the scoped dependencies: infrastructure, security review, integrations, distribution of the apps to your users and your acceptance criteria.
Procurement Support
A Sover proposal is written for your project, and it spells out the points a procurement team should never have to assume. Terms from another distributor or another deployment do not carry over to your agreement.
The user scope, the hosting model, the required features and the integrations the proposal covers.
Sover issues the commercial documents for a Sover-only project. The agreement identifies the contracting party and who is responsible for each part of the proposed deployment.
Source-code licensing and rebranding are not included automatically. Where you take them, the proposal names the rights, deliverables, maintenance responsibilities and any app-distribution work.
The Sover SLA is part of your agreement: Standard Support included, Premier Support where you take it, with severity levels and initial response times defined.
Service Level AgreementDirect or through a Partner
Partners work with Sover as system integrators and resellers, as channel partners who refer and introduce customers, or as technology partners. Partner terms are not published: tell us what you would bring.
Distributes the platform globally, and issues the commercial documents for a Sover-only project.
Distributes Sover only together with the IREX Ethical AI Platform and/or to existing IREX clients. Within that scope, IREX commercial terms apply.
Visit IREXSover and IREX are related parties. They share one team, and Sover is majority-owned by IREX co-founder Nik Ptitsyn.
Tell us your user scope, hosting model and the features and integrations you need, and we will get back to you.
Define the user scope, hosting model, required features, integrations, and support responsibilities for your project, then request a proposal for that scope. Terms from another distributor or deployment should not be assumed to apply to your agreement.
An annual subscription (SOVER-MESSENGER-1Y) is licensed per user, per year. A perpetual license (SOVER-MESSENGER-PERP) is licensed per user with three years of support included, and support can be extended with SOVER-MESSENGER-EXT.
Sover issues the commercial documents for a Sover-only project. The agreement identifies the contracting party and the responsibilities for the proposed deployment.
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.
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.
The schedule depends on infrastructure readiness, security review, integration work, client distribution, and acceptance requirements. Establish a project plan after those dependencies are scoped rather than treating a generic rollout duration as a commitment.
Support response times are set by the Sover SLA: under Premier Support, initial response within one hour for urgent issues and two hours for high-impact issues. Availability and recovery commitments are set for the agreed deployment and statement of work; there is no universal uptime, recovery-time, or acceptable-data-loss figure to apply to every installation.