Sovereign foundation · Roadmap
Provide one customer-operated identity layer for users, services and applications, with federation, role-aware access, lifecycle controls and reviewable administration.
Status: Roadmap. This application is being developed for open-source release. Its repository, OSI-approved software licence, model-specific terms, version, provenance and supported deployment modes will be published with the applicable release.
Planned replacement scope
Roadmap scope: designed to replace or consolidate organisational directories, SSO, identity federation, account provisioning and access-lifecycle platforms. Migration would preserve authoritative sources, authentication methods, recovery paths, service identities and audited access before legacy identity systems are retired.
Core capabilities
Exact coverage, deployment requirements and limitations are documented for the selected version and use case.
Operate an authoritative directory where appropriate or integrate with approved identity sources and federation arrangements.
Give users consistent authentication across approved SovereignEU and connected organisational applications.
Connect joining, changing roles and departure to account creation, entitlement review, suspension and removal.
Govern human and service identities through scoped roles, administrative boundaries and reviewable access history.
Product boundary
Identity & Access Management supplies authenticated identity and roles. Each application remains responsible for its permissions, purpose boundaries and records, while AI Defense monitors relevant security signals.
Adoption outcome
Inventory users, service accounts, authoritative sources, federation, recovery and application dependencies, then migrate through tested coexistence and rollback stages.
Sovereignty matrix
Product-specific answers are established through the deployment architecture and dated evidence record.
Connected Roadmap capabilities
Every connected capability shown here is part of the current Roadmap.
A practical first step
Inventory users, service accounts, authoritative sources, federation, recovery and application dependencies, then migrate through tested coexistence and rollback stages.
