For an enterprise, AI sovereignty starts with this primary requirement: Retain control of its own data and infrastructure. But as organizations move from experimenting with AI to deploying it in real business processes, control over the models themselves has become increasingly important. This includes the ability to fine-tune and adapt models to the specific work the enterprise needs them to do. Atos is doing exactly that with Red Hat AI, in a project focused on parsing German-language social media content across 14 categories, such as indicators of harmful content.

To remain reliable for downstream systems, the model must deliver its insights in a consistent, defined JSON structure. At the same time, the solution must meet strict sovereignty requirements, with control over the data, models and training pipeline. For this to work, Atos had to find an approach that could deliver the required accuracy and reliability, while also remaining both sovereign and economically viable at scale. RAG has become an important way for enterprises to connect AI models to proprietary information. But not every problem can be solved by giving a model more context.

For Atos, the challenge was getting a model to reliably perform a specific task: Interpret primarily German-language content, extract the right information, and consistently return it in the required structure. That requires changing how the model behaves rather than simply what information it has access to. With Red Hat AI, Atos was able to use synthetic data generation to create the high-quality datasets needed to fine-tune small models for structured extraction.

This addresses the scarcity of domain-specific data (a common fine-tuning hurdle), allowing enterprises to generate synthetic training sets needed to specialize a model for a particular enterprise task. This gives an enterprise another way to connect its data to AI. RAG can provide models with relevant enterprise knowledge, and fine-tuning can be used when the goal is to teach a model more specialized and consistent behavior. Why do this rather than simply using a frontier model? At enterprise scale, model size matters.