Authorised signals
Administrators define the purpose, event sources, access and retention. Customer content is not training data by default.
SovereignEU Applications
AI applications being built for public-source release.
Every SovereignEU application is being developed for release under a branding-protected Community Licence. Source access, permitted adaptation and required product identity will be stated precisely with each release.
Status: Roadmap. This application is being developed for public-source release under a branding-protected Community Licence. Its repository, exact rights, branding conditions, version and supported deployment modes will be published with the applicable release.
Application portfolio
Defined tools for defined organisational work.
Adopt one workflow at a time and connect it to shared identity, knowledge and control services.
Applications
SovereignEU Documents
AI-native document and records management with permissions, provenance and lifecycle controls.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Applications
SovereignEU Knowledge
Governed, time-aware organisational knowledge with reviewed AI-assisted updates.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Applications
SovereignEU Workplace
Open, AI-native authoring and collaboration introduced alongside existing tools.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Applications
SovereignEU Intranet
Internal publishing and discovery for pages, policies, news and organisational resources.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Applications
SovereignEU Service Desk
Governed request intake, triage, self-service, escalation and resolution evidence.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Applications
SovereignEU Projects
AI-assisted projects, issues, releases, dependencies and delivery monitoring.
Status · Roadmap
Source-available Community release planned
On-premises improvement loop planned
Defining Roadmap capability
Every application is being designed to improve locally.
Each SovereignEU application is being designed to participate in a customer-controlled improvement loop. Authorised events and outcomes can be analysed inside the deployed environment to propose and evaluate changes under explicit approval, audit and rollback rules.
Local graph engineering
A time-aware graph connects workflow evidence, candidate changes, evaluations, approvals, releases and measured outcomes.
Controlled release
Customer policy determines what is suggestion-only, what requires named approval and which predefined low-risk changes may proceed automatically.
Public-source commitment
Source access and branding terms should both be explicit.
Each released application will identify its Community Licence, permitted use and adaptation, required product identity, version, dependencies, interfaces and deployment conditions.
Inspect
Review the published source, Community Licence and documented component provenance.
Operate
Run the software with your own teams and infrastructure while retaining required identity and notices.
Adapt
Configure and extend permitted workflows through documented interfaces under the published terms.
Choose support
The planned Enterprise path can add rebranding rights, dedicated engineering and contractual accountability.
Staged adoption
Coexist, validate, then expand.
Migration begins with identity, data ownership, supported formats, synchronisation direction, conflict handling and a tested export path.
- 01Choose one workflow
Define users, owners and measurable acceptance criteria.
- 02Connect deliberately
Map identity, data and integration responsibilities.
- 03Verify operation
Test permissions, accessibility, recovery and export.
- 04Expand by evidence
Add teams and applications after operational acceptance.
A practical first step
Start with the application that solves today’s problem.
Define a bounded use case that can coexist with your current environment.