SovereignEU Enterprise · licensing model planned
Under the intended model, Community releases will retain SovereignEU product identity. Enterprise agreements can grant rebranding, co-branding or white-label rights and add dedicated support, personalisation, integration and deployment on infrastructure you control.
Community and Enterprise
Under the planned model, once released, an application can operate with SovereignEU identity under its Community Licence or under an organisation’s identity through an executed Enterprise Licence.
Under the intended model, Enterprise would be optional for standard branded use. An executed Enterprise Licence would be required to remove, replace, obscure or materially reposition protected SovereignEU product identity unless specific written permission applies. The Enterprise Licence governs branding rights; a separate services-and-support schedule defines delivery and service commitments. Product availability and final terms remain release- and agreement-specific.
Enterprise services
The engagement is scoped around your systems, data, deployment boundary and internal capability. Exact deliverables and service commitments are contractual, not implied by this page.
Apply licensed organisation identity, visual themes and workflow-specific experience within the agreed scope.
Named channels, supported versions, priorities, escalation and response targets defined in the agreement.
Establish identity, roles, retention, model routing, connectors and administrative controls for the selected use case.
Connect existing applications, document stores, databases, APIs and data through a staged, testable migration plan.
Design, install and harden the supported stack in customer premises or a customer-controlled private environment.
Provide administrators, developers, users and security teams with documentation, runbooks and practical training.
Accountable delivery
The objective is not only installed software. It is a verified deployment with clear ownership, documentation and a team capable of operating it.
Map the workflow, infrastructure, data, integrations, risks and acceptance criteria.
Adapt identity, policy, interfaces, existing applications and approved information sources.
Install in the agreed environment and test quality, security, recovery, usability and exit.
Operate through defined support paths while transferring runbooks, configuration and skills.
Protected product identity
The intended licensing model defines the branding boundary; repository history, signed releases, inventories and traceable artefacts must establish technical provenance.
Planned Community terms will require the defined SovereignEU identity, attribution and product notices to remain visible.
Teams will be able to inspect, self-host and adapt functionality within the exact rights published for the release.
An executed agreement can permit rebranding, co-branding or white-label operation for named products, entities and environments.
White-labelling never removes upstream copyright, licence or attribution obligations; customer-specific work must be identified and licensed separately.
Contract boundary
An executed Enterprise Licence and services schedule must state the rights granted, what is supported, who may access the environment and what the organisation receives at handover.
Common questions
A practical first step
Define the products, environments, branding rights, integrations and support responsibilities in scope.
