We designed and deployed a sovereign AI platform over 14 weeks. Infrastructure deployment (weeks 1-5): sovereign GPU infrastructure. Hardware: 8x NVIDIA H100 GPUs deployed in the group's Frankfurt data centre — the existing data centre having available rack space, power (each H100 requiring ~700W), and cooling capacity. The GPUs installed in a dedicated rack with: independent network segment (no connectivity to general corporate network — access controlled through a dedicated jump host), independent storage (NVMe storage for model weights and inference data — encrypted at rest with the group's key management system), and physical security (the GPU rack in a restricted-access zone within the data centre — access logged and controlled). Network: the AI platform accessible only from the corporate network — no internet connectivity. Applications connecting through internal API endpoints. Users: accessing through the group's internal web applications — never directly interacting with the AI infrastructure.
Inference stack: vLLM deployed on the GPU cluster — providing: high-throughput inference (continuous batching serving multiple concurrent requests efficiently), API compatibility (OpenAI-compatible API — enabling applications to be built using familiar SDKs and patterns), and model switching (multiple models loaded simultaneously — different use cases using different models). Model deployment (weeks 3-7): German-capable, domain-optimised models. Base models: Llama 3.1 70B (primary — strongest general capability for German language tasks), Mixtral 8x7B (secondary — efficient for high-throughput, lower-complexity tasks), and Llama 3.1 8B (tertiary — for simple classification and extraction tasks where speed matters more than capability). German evaluation: each model evaluated on German financial services tasks — document understanding (extracting information from German-language financial documents), regulatory analysis (understanding German regulatory text — DSGVO, BaFin circulars, compliance requirements), and customer service (generating helpful, accurate, formal German responses to banking queries). Fine-tuning: LoRA fine-tuning of Llama 3.
1 70B on: 15,000 German financial document examples (anonymised customer documents — loan applications, account opening forms, insurance claims), 5,000 regulatory question-answer pairs (DSGVO, BaFin, MaRisk — questions and expert-verified answers developed with the compliance team), and 8,000 customer service interaction examples (anonymised call centre transcripts — query and appropriate response). The fine-tuned model: significantly outperforming the base model on German financial services tasks — 23% improvement on document extraction accuracy, 18% improvement on regulatory question answering. RAG deployment (weeks 5-9): grounding AI in the group's knowledge. Knowledge base: ingesting the group's regulatory and compliance knowledge — BaFin circulars (200+), MaRisk (minimum requirements for risk management), DSGVO and BDSG (federal data protection law), insurance regulation (VAG, VVG), internal compliance policies (1,800 pages), and product documentation (banking products, insurance products, investment products).
Self-hosted RAG: embedding model (multilingual-e5-large) running on the same GPU infrastructure, Qdrant vector database on the same isolated network, and the retrieval-generation pipeline entirely within the sovereign perimeter. No data — documents, embeddings, queries, or responses — leaving the Frankfurt data centre. Application development (weeks 7-12): three AI applications. Document processing: AI-powered document extraction — customers uploading identification documents, financial statements, and application forms → the AI extracting: personal information (name, address, date of birth), financial data (income, assets, liabilities), and document classification (type of document, validity). Processing 200,000 documents annually — previously 100% manual, now AI-assisted with human verification. Compliance analysis: the RAG system providing compliance officers with AI-assisted regulatory analysis — officers querying the system with compliance questions, receiving answers grounded in the group's regulatory knowledge base with citations. "Welche MaRisk-Anforderungen gelten für die Auslagerung von KI-Diensten?" (What MaRisk requirements apply to outsourcing AI services?
) → the system retrieving relevant MaRisk sections, BaFin circulars on outsourcing, and internal policy — synthesising a cited response. Customer service assistant: banking call centre agents using an AI assistant — when a customer calls with a query, the agent describes the question, and the AI assistant provides: the relevant product information (from the product knowledge base), applicable regulatory requirements (from the compliance knowledge base), and a suggested response (in formal German, appropriate for customer communication). The agent reviews and delivers the response — the AI assistant accelerating response time while maintaining human oversight. Security and compliance (weeks 10-14): meeting BaFin and BSI standards.
BSI IT-Grundschutz: implementing BSI controls for the AI platform — comprehensive documentation (system architecture, security controls, operational procedures), access controls (role-based access — different roles for developers, operators, and users), logging (all AI interactions logged — query, response, model used, latency, user identity — logs stored in the group's SIEM), and vulnerability management (regular security scanning of the inference stack, OS, and network components). BaFin model governance: documenting: model selection rationale, training data description (sources, volume, content types), evaluation results (accuracy metrics on domain-specific benchmarks), known limitations (model failure modes, German language limitations, domain knowledge boundaries), and model version control (every model version tagged, stored, and recoverable). GDPR compliance: data protection impact assessment (Datenschutz-Folgenabschätzung) completed — assessing the AI platform's processing of personal data, identifying risks, and documenting mitigations.