Guide

AI knowledge base 2026: what has changed

What's different about AI knowledge bases in 2026 compared to two years ago — legally, technically, and in terms of what actually makes sense for small businesses.

Quote on Request6 to 10 WeeksAs of 2026
In short

Two things changed for AI knowledge bases in 2026: The transparency requirements of the EU AI Act have been in effect since August, and search engines now answer more and more questions directly in the results. Technically, reliability has improved most of all — which doesn't mean every project makes sense.

01 — Current

What changed recently

Two developments shape the decision in 2026: First, the transparency requirements of the EU AI Act have been in effect since August — anyone communicating with an AI system must be able to recognize it. Second, search itself now answers more and more questions directly, which changes the value of having your own easily findable information source.

For AI knowledge bases, this means in practice: labeling is mandatory, not a stylistic choice, and the content the system works with is the same content that gets cited in search results and generated answers. If you prepare it properly once, you use it twice.

Technically, reliability has improved most of all. What was still an experiment two years ago is today a plannable implementation in many cases — which doesn't mean every project makes sense.

02 — Legal situation

EU AI Act: what applies

Since August 2026, the transparency requirements from Article 50 of the EU AI Act apply: Anyone communicating directly with an AI system must be able to recognize it. We build in the labeling as standard.

The AI Act doesn't distinguish by company size: A sole proprietorship with an AI system in customer contact is affected just as much as a corporation. What matters is purpose and risk, not headcount.

There's also the obligation to ensure adequate AI competence for the people working with it. That's not an examination requirement, but it should be documented — a training session with a participant list is the simplest proof.

03 — Benefits

What it actually delivers

  • Time that's missing elsewhere. New people need months to figure out where everything is. Experienced staff get constantly interrupted because they're the only ones who know.
  • Consistent quality. A system doesn't have a bad day and doesn't skip a step — regardless of who's currently in the office.
  • Traceability. What runs automatically is documented. That helps with handovers, vacation coverage, and in case of disputes.
  • Availability outside business hours. A significant portion of inquiries arise in the evening and on weekends — where until now no one was responding.
  • A side effect hardly anyone plans for: During setup, it regularly becomes apparent that processes in the business are unclear. Clarifying that is often more valuable than the automation itself.

04 — Questions

Frequently asked questions

Can we roll this out to more departments step by step?

Yes, that's the usual approach. Start with one department, learn from their questions and results, then connect the next one — rather than releasing everything at once.

How do we detect outdated answers?

Through date references and marking of documents flagged as obsolete. Analytics also show which sources are used most often — those you maintain first.

What is RAG?

The abbreviation stands for retrieval-augmented generation. Instead of having the language model answer from memory, your documents are searched first, and only the passages found are used to generate the answer. That's why the answer has a source.

What if we have multiple languages in our document base?

No problem — the search understands questions and documents regardless of language and finds the right answer even when the question and source are written in different languages.

Does this have to run in the cloud?

No. For sensitive areas, we use models that run entirely on your own hardware. That costs more to set up and slightly reduces answer quality, but no document leaves the building.

Our documents are a mess. Will it still work?

To a certain extent, yes — the system handles different formats and structures. What it cannot do is resolve conflicting information. If three versions of a price list are in circulation, you need to clarify which one applies first.

Will everyone see everything?

No. The permissions from your existing systems are carried over. If someone isn't allowed to open a folder today, they won't get answers from it either.

Next step

Send us a few sentences about your project.

We read every inquiry ourselves and respond personally. No sales team, no callback form into the void.