Chorus stays on-prem: when “sovereign cloud” is not enough to move an ERP

You run an ERP—or a heavy line-of-business system—and slides talk about “sovereign cloud.” In meetings it sounds like a migration date. On the ground, nothing moves: servers still sit in your rack or at a conventional host, because no one signs off on an offer that combines security, vendor certification, and your real database size. The French State faces the same tension with Chorus, the SAP system behind public budgeting and accounting. Until a SecNumCloud cloud can host the SAP application itself on acceptable terms, the core stays on-prem—even while other services already live in qualified cloud.

Why Chorus has not left the server room

The Agence pour l’informatique financière de l’État (AIFE) operates Chorus at the heart of budget and accounting processes. In an October 2025 report on public-sector IT sovereignty, the Cour des comptes noted Chorus remained on-prem, for lack of a credible alternative: SecNumCloud qualification, SAP-certified hardware, capacity for Hana volume, and access via the State interministerial network. That is not bureaucratic fuss—it is the same equation as an SMB or mid-market firm on SAP hitting a wall when asked to shift production to a “trusted” cloud that still mostly covers infrastructure layers.

Usage-wise, Chorus has roughly 25,000 direct users plus 43,000 through an interfaced solution. Dozens of satellite applications orbit it, often still on ministries’ internal infrastructure. Moving the ERP core is not a hosting change—it is resilience, connectivity, and scope work.

2027: a study, not an announced cutover

After SAP’s announcements on a French cloud region, AIFE says it will launch a 2027 study on whether a SecNumCloud offer could meet modernisation and resilience needs—including keeping the financial SI running after a major event on national territory. Emmanuel Spinat, AIFE director, stresses months of talks with SAP on the gap between a “sovereign” pitch and a SecNumCloud-compliant offer, and caution on vendor timelines. The wording is explicit: a perspective, not an immediate answer to the Chorus roadmap.

SAP SCI France: infrastructure first, labelled ERP later

SAP is preparing Sovereign Cloud Infrastructure France (SCI France)—three datacenters in Île-de-France, targeted to open in Q2 2027, with S/4 Hana Cloud Private Edition, BTP, and IBP in the initial catalog. The vendor cites investment of up to €300M by 2032 (announced at Choose France). Partnerships with Bleu and S3NS already support hosting discussions on qualified infrastructure, but labels obtained so far mainly cover IaaS/PaaS, not yet the full ERP application stack.

The SecNumCloud file for SAP’s offer as a whole can start only when SCI France opens. Given ANSSI processing times, a SAP offer qualified for the application layer would not be available, at best, until late 2028 or early 2029—a horizon discussed at the USF convention in mid-October 2026 and echoed in press coverage on Chorus. The 2027 study can progress while the target offer still does not exist in labelled form.

Already hybrid—the pattern worth copying

AIFE is not “anti-cloud.” Its site describes a hybrid architecture: Chorus and several legacy apps stay on AIFE infrastructure; Place, TNCP, PISTE (API platform, SecNumCloud since 2023), and the public e-invoicing portal are or will be in qualified cloud, including OVHcloud. For a business leader, the lesson is not “wait for SAP”: segment what can move to SecNumCloud today, what must stay on-prem for lack of application qualification, and what needs a continuity plan that does not rely on vendor marketing.

If you are renewing hosting or modernising an ERP and weighing on-prem, trusted cloud, and vendor promises, we can map a timeline to what is actually qualifiable today.