Oktawave’s Sovereign-Cloud Direction: Portability, Federated Identity and Confidential Computing

November 16, 2026

Illustratie bij Oktawave’s Sovereign-Cloud Direction: Portability, Federated Identity and Confidential Computing

From IaaS to an interoperable security layer

Oktawave’s selected articles describe three related areas of development around its Polish cloud infrastructure. In the Next Gen Cloud project under the European IPCEI-CIS initiative, the provider says it has moved into detailed design and Proof-of-Concept preparation for a highly available, federated identity and access management environment based on OpenStack Keystone. The proposed design combines multi-domain tenancy with RBAC and ABAC authorization models and is intended to support multi-cloud platforms and external identity providers. Separately, Oktawave advocates exit-ready architectures built around workload classification, data-portability planning, open standards, containers, Kubernetes, Infrastructure as Code, DevOps and GitOps. Its security work extends this approach through a proposed software-defined key-management architecture using Trusted Execution Environments, confidential computing, post-quantum algorithms, format-preserving encryption and secure multi-party computation. Oktawave says these technologies are intended to underpin TrustVault, a product planned for its commercial portfolio, including confidential GPU processing for data-intensive AI and machine-learning workloads.

A European cloud strategy built around control rather than isolation

Taken together, the articles indicate a strategy to differentiate Oktawave’s IaaS through interoperability, customer control and European digital-sovereignty requirements rather than through a closed stack of proprietary services. Federated IAM would provide a common authorization layer across distributed environments; exit-ready engineering would make movement between providers, private infrastructure and hybrid deployments more practical; and customer-controlled cryptographic keys could reduce the amount of trust placed in cloud operators and administrative layers. This suggests an emerging direction in which a regional provider acts as a secure component of multi-cloud architecture rather than demanding that every workload remain on one platform. The technology direction also links operational resilience with security: identity federation, repeatable deployment, workload portability and protection of data in use are treated as parts of the same architectural problem. For Eastern European organizations facing EU regulatory obligations, this combination may be more relevant than a simple appeal to local hosting, particularly in finance, healthcare, government and critical infrastructure.

Ambitious engineering still needs production evidence

The material is provider-authored and should be read as a statement of work and direction, not independent validation. The federated IAM initiative is still at design and PoC-preparation stages: Oktawave lists installation, external identity-provider integration, implementation and verification testing as subsequent steps. Likewise, the TrustVault article describes intended commercial availability and makes strong claims about exclusive key control, hardware isolation, compliance support and HSM-like protection, but supplies no independent audit results, certification details, benchmarks, service-level commitments or production case studies. Intel SGX, confidential GPU processing, MPC and post-quantum cryptography also introduce implementation, hardware-dependency and operational-complexity questions that buyers must test against their workloads. Exit readiness itself is not automatic: containers and open interfaces can improve portability, but data gravity, network design, managed-service dependencies, identity mappings, egress charges and application refactoring may still complicate migration. Buyers should therefore distinguish architectural compatibility from a tested ability to move critical services within required recovery times.

Decision guide and sources: Oktawave’s federated IAM project update

For IT decision-makers in Poland and wider Eastern Europe, Oktawave’s direction merits attention where procurement priorities include EU-aligned sovereignty, hybrid or multi-cloud operation, controllable encryption and a credible path away from provider concentration. Evaluation should nevertheless be tied to measurable evidence: request a working IAM federation demonstration, documented failure and recovery behavior, tested RBAC and ABAC mappings, supported identity-provider integrations, key-custody procedures, hardware and software dependencies, independent security assessments, and contractual export and termination provisions. Organizations considering regulated or AI workloads should also verify whether confidential GPU processing, post-quantum mechanisms and TrustVault are production services or roadmap components at the time of procurement. Finally, run an actual exit exercise that measures data-export time, application portability, costs and service restoration rather than accepting architectural intent as proof. The underlying provider material comprises the federated IAM design and PoC update, the cloud-exit strategy guidance and the Next Gen Cloud confidential-computing and TrustVault description.

Get the Cloud Insights weekly roundup

The week's most important stories on cloud, sovereignty and infrastructure, every Thursday in your inbox. Free.

We will email you to confirm first. Unsubscribe any time. Privacy policy

Leave a Comment