How a Russian IT Company Turned Corporate Knowledge into a Working RAG System

Tsifra, a company working in industrial digitalization, has published a detailed breakdown of its corporate RAG system. Rather than pay for costly fine-tuning of language models, its engineers built a pipeline with local vector search, reranking and context assembly for a cloud LLM. The team paid particular attention to information security: sensitive data is filtered locally before anything is sent to the cloud. The system prompt strictly ties answers to facts and primary sources, which minimizes hallucinations. The case shows how Russian companies approach knowledge management under restrictions on the use of cloud AI services.

AI-processed from Habr AI; edited by Hamidun News
How a Russian IT Company Turned Corporate Knowledge into a Working RAG System
Source: Habr AI. Collage: Hamidun News.
Listen to article

The problem of corporate memory is familiar to any technology company that has passed the 100-employee mark. Documentation is scattered across dozens of systems, expertise is locked in the heads of key people, and a new engineer spends weeks looking for the answer to a question someone solved six months ago. Engineers at Tsifra, a Russian developer of platform solutions for industry, decided to attack this problem systematically and built a full RAG pipeline for internal use.

RAG, or Retrieval-Augmented Generation, has long since stopped being exotic in the world of enterprise AI. The idea is simple: instead of hoping the language model "remembers" the right information, the system first finds relevant documents in a knowledge base and then passes them as context for generating the answer. But between a neat architecture diagram and a working product lies a chasm of engineering decisions, and these details are what make the Tsifra case genuinely valuable for the industry.

The architecture, described by Dmitry Omarov, lead engineer at the training center, and his colleague Fyodor Arefyev, rests on several key principles. The first, and perhaps the most important, is a deliberate decision not to fine-tune language models. Fine-tuning a corporate LLM sounds appealing in presentations, but in practice it is an expensive process that requires constant updates whenever the documentation changes.

The team bet on a dynamic knowledge base: documents are indexed, converted into vector representations and stored locally. When an employee asks a question, the system finds the most relevant fragments through vector search, then runs the results through a reranking stage, an additional ranking pass that filters out noise and improves the precision of the results. Only after that is the assembled context sent to a cloud language model to generate the final answer.

The approach to information security deserves separate attention, as it is a painful topic for any company working with industrial customers. Sending internal documents to a cloud AI service without filtering is a direct path to a data leak. Tsifra's engineers implemented a local sanitization layer: before the context leaves the company perimeter, sensitive information is automatically removed from it. It is an elegant solution that lets the company use the power of cloud LLMs without compromising on security. In effect, the company gets the best of both worlds: local control over its data and the generation quality that only large cloud models provide.

Fighting hallucinations is another front where the team achieved notable results. Language models tend to generate plausible-sounding but factually wrong information, and in a corporate context that is unacceptable. A wrong reference to a regulation or an erroneous technical recommendation can have real consequences on the factory floor. The solution turned out to be partly engineering, partly methodological: a carefully designed system prompt strictly constrains the model, requiring it to rely exclusively on the provided context and to accompany every answer with links to primary sources. If the knowledge base has no information to answer with, the model must say so honestly rather than make something up.

This case matters less for its specific technical decisions than for its overall approach. Russian companies operate under particular conditions: access to leading cloud AI platforms is restricted, regulators' requirements for data processing are strict, and budgets for AI infrastructure are far from unlimited. In this reality, RAG systems with a local search layer and controlled interaction with the cloud are effectively becoming the standard architecture. They let companies balance quality, cost and security, three parameters that in enterprise AI are almost always in conflict with one another.

Tsifra's experience also illustrates a broader trend: in 2026, enterprise AI is no longer about experimenting with chatbots but about knowledge management infrastructure. Companies that learn to make their collective expertise accessible through intelligent search will gain a measurable competitive advantage. Onboarding time for new employees shrinks, re-solving already solved problems becomes a thing of the past, and critical information stops being hostage to individual experts. In effect, a RAG system turns corporate memory from a passive archive into an active working tool, and that is where its real value lies.

Story
ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…