Bring your delivery, integration and customer relationships to governments and regulated organizations. Sover supplies the platform and the controls; the customer decides how they are used.
Ways to Partner
Each partnership is scoped around real projects, and its terms are agreed with Sover. Tell us what you do and the markets you serve, and we will talk it through.
Deploy Sover for your customers on their own servers with the Sover Private Cloud, on their Kubernetes clusters or on their virtual machines, integrate it with their systems and resell it. Branding scope, application distribution and delivery responsibilities are agreed for each project.
Introduce Sover to a government or regulated organization that needs control over its communications. Talk to Sover about how an introduction works before you make it.
Supply products or services that extend what the platform can do and how it is delivered. Tell Sover what you would add and where it fits.
Who We Work With
IT solution providers to state and city governments, in particular custom software developers and private cloud operators.
Developers of e-government portals and integrators of digital public services.
IT solution providers to national healthcare systems.
Distribution
Sover distributes the platform globally. IREX distributes Sover only together with the IREX Ethical AI Platform and/or to existing IREX clients.
Sover and IREX are related parties. They share one team, and Sover is majority-owned by IREX co-founder Nik Ptitsyn.
Visit IREXWhat Sover Brings
Source-code licensing is available. The license scope, permitted changes and maintenance responsibilities are set in the agreement for each deployment.
Sover is rebrandable, so the apps can ship under the customer's own name and brand. The branding scope and application distribution are agreed for the project.
Sover is user-hosted, on the customer’s own servers with the Sover Private Cloud, on their Kubernetes cluster or on their virtual machines. It is not a public multi-tenant cloud service.
A documented Bot API, 50+ REST methods with a Python client library, brings messages and actions from your customers' systems into Sover conversations.
Independent Sover instances federate, so organizations can work together while each controls its own instance and limits what crosses to other instances.
Sover neither owns nor accesses customer messages. Message history, credentials and application state stay under the customer's control on its own hardware.
Technology Partners
Technology partners supply products and services that extend what the platform can do and how it is delivered.
Tell us the markets and customers you serve, the work you deliver and how you would like to work with Sover.
No. Each partnership is scoped around real projects, and its terms are agreed with Sover. Tell us what you do and the markets you serve, and we will talk it through.
Partners close to public digital services: IT solution providers to state and city governments, in particular custom software developers and private cloud operators; developers of e-government portals and integrators of digital public services; and IT solution providers to national healthcare systems.
Sover distributes the platform globally. IREX distributes Sover only together with the IREX Ethical AI Platform and/or to existing IREX clients. Sover and IREX are related parties. They share one team, and Sover is majority-owned by IREX co-founder Nik Ptitsyn.
Yes. Sover is rebrandable, so the apps can ship under the customer’s own name and brand. The branding scope, application distribution, and delivery responsibilities are agreed for the project.
Source-code licensing is available. Its scope and commercial terms must be agreed: the proposal identifies the rights, deliverables, permitted changes, maintenance responsibilities, and any application-distribution work included.
Yes. Sover provides a documented Bot API, 50+ REST methods with a Python client library, for integrations that bring messages and actions into the communication environment. Scope each integration around the source system, target conversations, permitted actions, and deployment requirements.
