CHUNK WORKS x ATOS CLOUD PLATFORM

The Sovereign Data Layer: True Multicloud with a guaranteed exit strategy vs hyperscalers

One Control Plane (Atos) One Sovereign Data Layer (CW) Any Cloud (Infra)

From Central Management to Sovereign Architecture

The Atos Cloud Platform (ACP) orchestrates workloads across public and private clouds. By adding Chunk Works as the foundational data layer, the dynamics change completely. Data no longer lives inside the provider's cloud, but in an independent layer that belongs to the client.

Without Chunk Works

Data is locked in Azure Blob, AWS S3 or VMware vSAN. Migration is painful, exit is expensive, and sovereignty depends on the provider.

With Chunk Works

Data lives in its own encrypted layer. Workloads run anywhere (ACP), but the data is independent, portable and vendor-free.

1. The New Architecture: Sovereign by Design

Atos manages the workloads. Chunk Works owns the data.

Atos Cloud Platform (ACP)

Single Control Plane & Orchestration

Governance Operations Security Monitoring
Sovereign Data Layer (The Invisible Backbone)

CHUNK WORKS

"Ciphertext-only, Distributed, Customer Key Custody"

🛡️ Client holds the keys
↔️ No Egress Tax
🧩 Cross-Cloud Parity

Public Cloud Providers

Microsoft Azure
AWS
Google Cloud
M365 / SharePoint

Private, EU & On-Prem

VMware
OpenShift
OVHcloud
IONOS Cloud

2. The Sovereign Exit Lane

Minimal egress through data locality makes multicloud realistic

True multicloud doesn't exist as long as egress fees penalise you for moving data. With Chunk Works as an intermediary layer, you pay no additional egress fees* to the data layer itself. This means you can migrate workloads (VMware, Azure, AWS) without having to "buy back" data from the provider.

VMware Exit Scenario: Need to leave VMware due to licensing costs? Chunk Works makes storage portable to e.g. OVH or Azure without expensive data migration projects. The chunks are already there.

Paradigm Shift

Old Model: Provider Sovereignty
New Model: Architecture Sovereignty

Sovereignty no longer depends on where the server is, but on who owns the encryption.

Why this works for Atos:

  • ✔ Buffer layer: Absorbs shocks such as VMware licensing changes or hyperscaler price increases.
  • ✔ Zero Trust: Even Atos cannot access the data (ciphertext-only + customer key custody).
  • ✔ True Multicloud: Data is available across 3 locations simultaneously (Parity).

The Workflow: From Cloud to Control

1

Atos Orchestrates

ACP manages the VMs, containers and applications on Azure, AWS or OpenShift.

2

Chunk Works Secures

Before data is written, it is encrypted and chunked. The key stays with the client.

3

Infrastructure Stores (Blind)

The encrypted chunks land on AWS S3, OVH or IONOS. The provider only sees noise, not data.

← Genesis Industries →