Smals, the shared IT organization serving over 300 Belgian public institutions, has entered a framework agreement designating Google Cloud as its primary cloud provider. The deal extends Google Cloud services and AI capabilities to Smals member bodies while preserving Smals' operational oversight of how those environments are configured and used.
What happened
The agreement positions Google Cloud as a third infrastructure pillar for Smals members. The organization already operates its own on-premise systems, participates in Belgium's governmental community cloud, and runs a private cloud environment spread across three Brussels-area data centers. Rather than displacing any of these tiers, Google Cloud gives members a further option for workloads with specific technical or compliance needs.
Smals CTO Dirk Deridder characterized the arrangement as expanding the technical toolkit available to member institutions while remaining within the security and sovereignty requirements that govern Belgian public sector IT. Kurt Rommens, Google Cloud's public sector lead for Benelux, framed the partnership around AI adoption by both Smals and its members, with explicit reference to portability and sovereignty standards set at the Belgian federal level.
- Smals serves more than 300 Belgian public institutions, including social security and healthcare bodies
- Google Cloud is designated the primary cloud provider under the framework agreement
- Existing infrastructure includes on-premise systems, a governmental community cloud, and a private cloud across three Brussels-area data centers
- Google has pledged €5 billion toward Belgian cloud and AI infrastructure over two years, announced in October 2025
- Google's Belgian presence dates to 2009, with its Saint-Ghislain campus now spanning five data centers across 90 hectares and a second campus under construction in Farciennes
Why it matters
The structure of this agreement reflects a pattern increasingly common in European public sector cloud procurement: hyperscaler access granted within a layered architecture that keeps sovereignty and operational control with the public body. Smals retains authority over how Google Cloud environments are deployed, meaning member institutions choose workload placement based on actual requirements rather than migrating wholesale to any single provider.
Google's declared €5 billion investment in Belgian infrastructure lends the partnership commercial weight beyond a standard procurement decision. That commitment, announced in October 2025, encompasses expanded capacity at the existing Saint-Ghislain campus and a new facility at Farciennes, reinforcing Belgium's position as a significant node in Google's European network.
What to watch
How Smals' member institutions actually distribute workloads across the four available tiers will be the practical test of whether the framework delivers on its stated flexibility. AI workloads are an explicit part of the rationale, so uptake of Google Cloud's AI services among Belgian healthcare and social security bodies could serve as a concrete indicator of how this kind of sovereignty-conscious hyperscaler arrangement performs in practice. Procurement frameworks in neighboring countries with similar public sector structures may take note of the model.
Companies mentioned
Automated pipeline · Cloud & Infrastructure
Synthesized from 1 industry feed on 14 Jun 2026. First draft failed editor review; a revised version was approved before publication. Style guide v1.2.
Sources
Decision trail
- Checking for duplicates — New story Smals adopting Google Cloud for Belgian public sector infrastructure is a new public sector cloud deal story.
- Writing the article — Draft created article_id=36 slug=smals-adds-google-cloud-as-third-infrastructure-tier-for-300-belgian-public-bodies
-
Editor review — Rejected
- Factual grounding — material: The source states 'Google Cloud becomes a third option alongside those existing pillars' (on-premise, governmental community cloud, and private cloud = three existing pillars, Google Cloud as a third external option). The article's Key facts block describes Google Cloud as 'a third external option,' but the body text (What happened section) calls it 'a fourth option' — contradicting both the source and the article's own Key facts block. The source does not support the 'fourth option' framing
- it explicitly calls Google Cloud a third option/pillar.
- Factual grounding — material: The source describes Google Cloud as Smals' 'primary cloud provider,' which is a significant characterization the article omits entirely. While the article's framing of a layered multi-tier architecture is not wrong, omitting 'primary cloud provider' while emphasizing it as merely one of several equal options may misrepresent the source's characterization of the relationship.
- Style compliance — minor: The article body (excluding Sources) is approximately 530 words for the prose sections plus the Key facts block. Word count appears within range, but the Key facts block contains five bullet items
- the style guide permits 3–5, so this is acceptable.
- Factual grounding — minor: The standfirst says 'without displacing existing on-premise or governmental cloud setups,' which is accurate, but also omits the private cloud tier already mentioned in the source, making the standfirst slightly incomplete in its characterization of existing infrastructure.
- Sources — minor: Only one source is linked (Hosting Discussion). The style guide requires synthesizing from ALL provided sources, but only one source text was provided, so this is not a violation. However, the single source link uses 'Hosting Discussion' as anchor text for a URL at hostingdiscussion.com, which appears accurate.
- Writing the article — Rewritten editor-driven rewrite
-
Editor review — Approved
- Style compliance — standfirst accuracy: The standfirst describes Google Cloud as 'a third pillar alongside existing on-premise, governmental community cloud, and private cloud infrastructure' — that correctly lists three existing pillars, making Google Cloud a fourth option, not a third pillar. The source says 'Google Cloud becomes a third option alongside those existing pillars' meaning the three existing pillars together, with Google Cloud as the third infrastructure option (after on-premise/gov cloud grouped, and private cloud). This is ambiguous but the standfirst's phrasing could mislead
- minor rather than material since the body corrects it.
- Style compliance — word count: Body word count is approximately 480 words of prose plus the key facts block (~80 words), totalling roughly 560 words excluding Sources. This is within the 450-620 word target.
- No copied phrasing: The phrase 'sovereignty concerns do not block hyperscaler access but do shape how organizations structure it' in the source is not reproduced verbatim
- the draft rewrites this concept adequately. Overall paraphrasing is acceptable.
- Factual grounding — 'third pillar' vs 'third option': The source says Google Cloud is 'a third option alongside those existing pillars' (i.e., a third infrastructure option beyond the grouped existing systems). The draft's Key facts block states 'Google Cloud is designated the primary cloud provider' which is correct, but the article body and standfirst call it 'a third infrastructure pillar' whereas the source calls the on-premise, governmental community cloud, and private cloud the existing pillars and Google Cloud the third *option*. This is a minor imprecision, not an invented fact.
- Assigning hero image — Pexels pexels_id=36376007
- Linking related stories — Linked 4 relations from 18 candidates
- Linking related stories — Linked 4 relations from 18 candidates
- Linking related stories — Linked 4 relations from 18 candidates
- Linking related stories — Linked 5 relations from 22 candidates
- Linking related stories — Linked 5 relations from 22 candidates
- Linking related stories — Linked 5 relations from 22 candidates
- Publishing — Published smals-adds-google-cloud-as-third-infrastructure-tier-for-300-belgian-public-bodies
Discussion · coming soon
Be the first to join the thread when community discussion launches.