Concept card

BARC — Reality Check: Sovereign Data Management – Made in Europe?

As of 2026-07-23

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is BARC — Reality Check: Sovereign Data Management – Made in Europe??

BARC frames "is SAP European enough?" as an open question, not a verdict — the study's actual vendor scores and gap rankings are paywalled, leaving only the framing question itself as usable, unverified content.

What it is

BARC's reality check on sovereign data management: an independent assessment of what data sovereignty actually requires in European estates, as opposed to what the term is used to sell (BARC — sovereign data management).

Why it matters

Sovereignty is now a live procurement criterion in European accounts, and it is unusually prone to being asserted rather than specified. "Sovereign" can mean data residency, operator jurisdiction, key custody, or supply-chain independence — four different requirements with four different costs, and a client who has not distinguished them will accept an answer that satisfies none of the ones that mattered.

For a consultant this is leverage. Being the person who separates the four is worth more than having an opinion about any of them.

How to use it

Use the assessment to build the client's own requirement statement rather than to recommend a product. Ask which of the four they are actually obliged to satisfy, by what instrument, and what evidence an auditor would accept. Most sovereignty conversations dissolve into a much narrower and more tractable requirement once that is on paper.

Why it matters in practice

The title itself is a question, not a claim — BARC is subjecting the "Made in Europe" vendor narrative to a reality check rather than endorsing it, which matters for how a consultant should cite it.
The relevant customer objection is named directly: SAP HQ is in Walldorf, but BDC runs on AWS/Azure/GCP underneath — a gap customers' procurement teams will probe.
Vendor names, capability scores, and gap rankings are explicitly paywalled — there is no verifiable numeric content to cite from this card alone.

Key points

Vendor-landscape complement to BARC's Data Sovereignty 2026 study (C273).
Title is a question — BARC reality-checks the 'Made in Europe' narrative, doesn't endorse it.
Examines what 'European' means across ownership / hosting / code-origin axes.
Vendor names, scores, gap rankings paywalled — title is the verifiable artefact.
BARC — Reality Check: Sovereign Data Management – Made in Europe? is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.
For AI use cases, measure reliability, cost, latency, safety, and human validation.

Terms used on this page

Data sovereignty: The principle that data is subject to the laws and governance of the nation/region where it is stored or processed. In procurement: a scoring criterion applied to cloud vendors.
Made in Europe: Marketing framing used by European cloud vendors to signal ownership, headquarters, and/or hosting within the EU/EEA — distinct from US-headquartered vendors running EU data centres.
Ownership axis: One of BARC's implied definitional axes for 'European': who owns the entity (European majority? US-listed?). Distinct from the hosting axis (where data resides) and the code-origin axis (where software was written).
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.
Adoption metric: The measurable behavior proving that the concept changed actual work after go-live.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks.

Open in the app →