What Scality and OVHcloud actually shipped
Scality and OVHcloud went public on 30 June 2026 with a joint storage platform that does something European buyers have wanted for years: deliver the object storage that modern applications expect without routing a single byte through a US hyperscaler. The stack pairs Scality RING and ARTESCA, both S3-compatible, with OVHcloud's On-Prem Cloud Platform and its HGR-STOR bare-metal servers. It can run as a 100 percent dedicated sovereign cloud or entirely on the customer's own premises, with backups replicated across multiple availability zones.
The two companies framed the launch around control rather than novelty. "Sovereignty is not a barrier to innovation, it is the prerequisite," said Emilio Roman, Scality's chief revenue officer. Sylvie Houliere Mayca, who runs OVHcloud's France, Belux and MEA business, tied it to the provider's record, calling it "a sovereign infrastructure backed by more than 25 years of OVHcloud expertise and ready for AI." The target buyers are named plainly: healthcare, finance, defence and public services, the sectors where GDPR, DORA, NIS2 and HIPAA turn data location into a hard requirement rather than a preference.
Why it matters: the S3 lock-in argument just weakened
The quiet significance is the S3 compatibility. For a decade the practical reason teams stayed on Amazon was not the raw storage but the API: applications, backup tools and data pipelines are all written against S3. An object store that speaks the same API without the same jurisdiction changes the migration maths. Moving off a hyperscaler stops being a rewrite and becomes a redirection, and the exit cost that quietly justified staying put drops toward the cost of copying the data.
That lands directly on the compliance desk. Under DORA a UK or EU financial firm has to show it can exit a critical cloud provider and keep operating; under NIS2 the same logic reaches far wider into essential services. A credible European object-storage tier that mirrors the S3 interface gives those teams the concrete alternative regulators keep asking to see. For a UK operator watching the FCA and PRA press on operational resilience, "we could move but it would take a year" is a weaker answer than "here is the sovereign tier we tested against."
The catch: sovereign is a build, not a checkbox
Yes, but sovereignty moves work back onto your side of the line. A dedicated or on-premises deployment means the customer, not a hyperscaler, carries more of the operational load: capacity planning, hardware refresh and the day-to-day running that AWS otherwise absorbs. Scality and OVHcloud published no pricing and no performance benchmarks with the launch, so the true cost against a comparable S3 bill is still an exercise each buyer has to run. Breadth of adjacent services, the long menu that keeps teams inside a hyperscaler, is also not a like-for-like match.
None of that cancels the shift. The offering is GPU-direct compatible and tuned for AI data pipelines, so training and MLOps can sit on the same sovereign tier instead of pulling regulated data back onto a US cloud to reach the accelerators. For an owner the useful question is no longer whether a sovereign object store exists - it now does, from two established European vendors - but which workloads have been sitting on a hyperscaler only because nothing else spoke S3.
Read next: One Supplier Breach Drove Half of Europe's Ransomware Victims | A German State Moves 50,000 Staff Off Microsoft
