Oktawave’s IaaS Direction: Portable, Federated and Confidential Cloud for Eastern Europe

November 16, 2026

Illustratie bij Oktawave’s IaaS Direction: Portable, Federated and Confidential Cloud for Eastern Europe

From cloud exit planning to federated identity and confidential computing

Three Oktawave articles outline a related set of infrastructure initiatives. The Polish provider says its European IPCEI-CIS Next Gen Cloud work has progressed from technology selection toward detailed design and a proof-of-concept environment for federated identity and access management. The planned architecture maps OpenStack Keystone onto Oktawave infrastructure, with high availability, multi-domain tenancy and hybrid role- and attribute-based access controls. Separately, Oktawave advocates exit-ready architectures built around workload inventories, portable data, containers, Kubernetes, Infrastructure as Code, open standards and tested migration procedures. Its security project adds software-defined key management, trusted execution environments, confidential computing, post-quantum algorithms and secure multiparty computation. Oktawave says these technologies are intended to underpin TrustVault, a forthcoming commercial product designed to keep cryptographic operations and data in use isolated from host operating systems and hypervisors. The provider also identifies confidential GPU processing as a possible foundation for sensitive AI and machine-learning workloads, although the articles do not describe a broader AI platform or service portfolio.

A sovereignty strategy based on control rather than isolation

Taken together, the initiatives indicate that Oktawave is positioning its IaaS around operational control across multiple environments. Federated IAM addresses who can access distributed resources; exit-ready architecture addresses whether applications and data can move; and confidential computing addresses whether infrastructure operators must be trusted with plaintext data or encryption keys. This combination is strategically relevant in Poland and wider Eastern Europe, where regulated organizations may need to reconcile cloud adoption with resilience, auditability and European digital-sovereignty objectives. The direction is not simply toward a nationally isolated cloud. OpenStack Keystone, external identity-provider integration, Kubernetes, open protocols and multi-cloud authorization instead suggest interoperability across public, private and hybrid infrastructure. Oktawave’s references to DORA, NIS2 and ICT concentration risk also show a commercial focus on finance, healthcare, government and critical infrastructure. Its AI direction is narrower but coherent: the emphasis is on protecting accelerated computation and sensitive datasets, not on presenting proprietary models as the main differentiator.

Ambitious security claims still require production evidence

The material describes engineering progress and intended capabilities, but buyers should separate architecture from demonstrated service maturity. The federated IAM work remains at the design and proof-of-concept stage, with installation, external identity-provider integration, implementation and verification testing listed as subsequent steps. TrustVault is described as forthcoming, so the supplied evidence does not establish production availability, service levels, customer deployments, performance overhead, pricing or operational scale. Claims that Intel SGX enclaves can technically prevent unauthorized access, that software-defined controls can provide HSM-like rigor, and that post-quantum mechanisms deliver future resistance are statements made by Oktawave rather than independent validation. Buyers should also examine hardware dependencies, enclave and side-channel threat models, key recovery, tenant isolation, audit results, algorithm lifecycle management and failure procedures. Portability likewise depends on more than containers: data volumes, managed-service dependencies, network design, identity mappings, egress costs and contractual support can still make an exit difficult. No tested migration times, recovery outcomes or comparative benchmarks are supplied.

Eastern European buyer guidance from the federated IAM project update, the cloud-exit guidance and the confidential-computing architecture

For IT decision-makers in Poland and Eastern Europe, Oktawave merits attention where infrastructure portability, European sovereignty and control of encryption keys rank above access to a very broad proprietary service ecosystem. The strongest signal is the architectural consistency across Oktawave’s federated IAM proof-of-concept, its exit-ready cloud recommendations and the proposed TrustVault security architecture: all three seek to reduce dependence on a single administrative or technology domain. A sensible evaluation should convert that direction into contractual and technical tests. Buyers should request current availability details, supported hardware and protocols, independent security assessments, identity-federation demonstrations, measurable recovery objectives and an executed workload-and-data exit exercise. They should also verify how responsibilities are divided among Oktawave, external identity providers and the customer. The provider’s direction is relevant to regulated regional IaaS procurement, but purchasing decisions should depend on demonstrated production operation rather than the ambition of the underlying research programme.

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