Europe 2026
What Breaks When You Build AI Under Sovereignty Constraints - Bilge Yücel, deepset GmbH
Overview
This talk explores the concept of AI sovereignty, defined as an organization's ability to design, deploy, and operate AI systems on its own terms. It breaks down sovereignty into four pillars: data, model, infrastructure, and operational control. The presentation highlights the challenges and trade-offs encountered when implementing AI systems under these constraints, particularly when moving from convenience-based SaaS solutions to more controlled, self-hosted environments.
Who should watch
- AI Engineers
- Product Managers
- Builders working with sensitive data
- Organizations needing to comply with strict regulations (e.g., GDPR, EU AI Act)
- Teams seeking to reduce vendor lock-in in their AI infrastructure
Key takeaways
- Sovereign AI requires explicit control over data flow, model choice, infrastructure, observability, and operations.
- Data sovereignty involves keeping data within trusted jurisdictions and managing access permissions rigorously.
- Model sovereignty means having the freedom to choose and switch models without significant architectural changes.
- Infrastructure sovereignty concerns where compute happens, with a spectrum from air-gapped environments to SaaS.
- Operational sovereignty focuses on monitoring, evaluation, versioning, and incident response in a traceable manner.
- Implementing sovereignty often involves trade-offs, such as increased complexity in managing infrastructure and data pipelines.
- Orchestration frameworks like Haystack can help manage complexity by providing consistent interfaces, explicit data flow, and versionable configurations.
- A sovereign architecture can incorporate guardrails for input and output, integrate self-hosted models, and ensure traceability through tools like OpenTelemetry.
Notable quotes
Sovereign AI is the ability of an organization to design, deploy, and operate AI systems on its own terms.
*...having explicit control over data flow, model choice, infrastructure, observability, and operations.*
Unofficial community note. Prefer the recording for nuance.