From the NVIDIA edition of October 21, 2026
NAND Research on GTC Berlin: factory-built AI factories and DPU-based agent enforcement are promising, but sovereignty at the data layer deepens dependence on NVIDIA's stack
NAND Research (Steve McDowell) · Industry analysis · Europe
- Publisher
- NAND Research
- Original publication
- 2026-10-21
- Source retrieved
- 2026-10-22
- Event date
- 2026-10-21
What happened
NAND Research's same-day analysis summarises the keynote (DSX POD, supply-chain capacity agreements, Google Cloud A5X Vera Rubin instances expected in November 2026, OpenShell Reference Architecture, extended Confidential Computing, Agent Knowledge Foundation, robotics and Hyperion) and gives a view: factory integration improves time to production 'only if power, site readiness, and partner execution keep pace'; DPU-based agent enforcement addresses a legitimate problem; but power, site readiness, supply-chain capacity, security effectiveness and partner execution will determine results. On sovereignty it argues that while NVIDIA offers more regional capacity and customisation, it 'deepens dependence on its hardware and software ecosystem', that open models do not ensure infrastructure independence when tools are tightly coupled to NVIDIA, and that buyers should measure promises against deployment speed, utilisation, reliability, cost and architectural flexibility while preserving choice and negotiating leverage.
Why it matters
Relevant to public buyers in Europe and to U.S. states adopting 'sovereign AI' language: it separates data and deployment control from technology independence, which matters for procurement strategy, exit planning and competition.
Evidence and measured results
Analyst opinion with disclosure that the firm may have advised companies mentioned; no new data. Summaries of announcements are consistent with NVIDIA's releases.
Limitations and uncertainty
Opinion; possible advisory relationships disclosed generically; no independent measurements.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-22; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Public buyers want sovereign AI but risk deep dependence on one vendor's stack.
- Stakeholders
- State or national CIO
- Procurement and legal
- Research computing leadership
- Discovery questions
- Which layers of sovereignty matter most: data, operations or technology?
- What exit and portability terms do you require?
- How will you measure utilisation and cost?
- Value hypothesis
- Interpretation: clear sovereignty definitions and exit provisions let buyers gain integrated-platform benefits with less lock-in.
- Potential engagement
- Sovereignty and vendor-dependency assessment for a public AI infrastructure plan.
- Unsupported claims
- That NVIDIA platforms provide technology independence
- Quantified lock-in costs
Pre-sales engineering
Role takeaway
- Fit
- Any public AI infrastructure design using NVIDIA platforms.
- Architecture and integration
- Dependency map of NVIDIA-specific and portable components.
- Prerequisites
- Component inventory
- Portability requirements
- Constraints
- Tight coupling of tools to the platform
- Security
- Agent enforcement effectiveness still to be demonstrated.
- Proof of value
- Port one model and serving stack to an alternative runtime as a test
- Document vendor-specific dependencies
Delivery
Role takeaway
- Work
- Define and report operating metrics and maintain a tested exit plan.
- Dependencies
- Metrics collection
- Contract exit clauses
- Ownership
- Programme owner with procurement and architecture.
- Skills and adoption
- Staff need skills to evaluate and operate portable components.
- Governance checkpoints
- Annual dependency review
- Exit plan test
- Acceptance criteria
- Proposed: utilisation, reliability and cost reported quarterly
- Proposed: portability test completed annually
- Risks
- Lock-in through platform-specific tooling
- Weakened negotiating leverage over time
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Tight coupling of tools and platform means portability needs deliberate design (open formats, alternative runtimes).
Governance
Who approves, reviews and stays accountable for outcomes?
Suggests evaluation criteria (speed, utilisation, reliability, cost, flexibility) for public AI infrastructure decisions.
Security and privacy
What data, permissions and controls need testing?
Notes security effectiveness of agent enforcement is still to be shown.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Not addressed.
Procurement
What should contracts, pricing and exit terms secure?
Recommends preserving choice and negotiating leverage, implying multi-vendor or exit provisions in public contracts.
Operating model
Which teams own the service once it runs?
Frames sovereignty as layered: data, deployment and technology, each with different control.
Publication history
- 2026-10-21NVIDIA · Issue 469 resources
Stable resource ID: nand-research-gtc-berlin-speed-security-sovereignty-tradeoff-20261021