Concept card

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

As of 2026-10-10

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

What is BARC?

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.

The regulatory frame is genuine and worth citing precisely rather than gesturing at: the EU Data Act governs access and switching obligations for cloud services (EUR-Lex — Regulation (EU) 2023/2854).

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.
This specific report is a hands-on technical evaluation, not a survey: BARC analyst T. Z. tests STACKIT (Schwarz Group's sovereign cloud) running a Dremio-based lakehouse against performance, scalability and cost.
84% of companies rated data sovereignty as strategically important in a recent BARC survey cited in this report — a stated-priority figure, not a technical-capability score.
Distinguishes three separate sovereignty questions: legal (which jurisdiction's law applies), strategic (dependency on one non-European supplier), technological (can an open-standards lakehouse match hyperscaler-native performance).
Vendor names, capability scores, and gap rankings beyond the STACKIT/Dremio case study are paywalled — the public framing question and the named technical evaluation are the verifiable artefacts.
Do not generalise a single-platform technical evaluation (STACKIT/Dremio) into a market-wide 'is SAP European enough' verdict — that is a different, unanswered question.
Complements C273 (Data Sovereignty 2026): C273 covers the strategic/roadmap framing, this report supplies the one piece of hands-on technical evidence BARC has published on a named European alternative.

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 informal way the market segments 'European': who owns the entity (European majority? US-listed?) — one lens among several (hosting location, code origin, operator jurisdiction); this specific BARC report instead tests a fourth lens directly: measured technical performance of a European-operated platform.
STACKIT: The sovereign cloud platform of Schwarz Group (the German retail group behind Lidl and Kaufland) — the specific platform this BARC report evaluates hands-on, running a Dremio-based lakehouse.
Dremio-based lakehouse: An Apache-Iceberg-native lakehouse/federated-query layer (the same underlying technology SAP acquired and integrated into Business Data Cloud, completed 2026-07-06) — here deployed on STACKIT as the technical subject of BARC's evaluation.
Hands-on practical evaluation (BARC methodology): BARC's approach in this report: direct performance measurement, scalability testing and cost assessment of a named, deployed platform — distinct from a self-reported practitioner survey (like the Trend Monitor, C278) or a vendor-briefing-based analyst rating.

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 · the facts worth quoting.

Open in the app →