Platform · Embeddings

Embeddings that make your knowledge findable

Searching thousands of documents takes more than keywords. Numaga turns your documents into embeddings — a numeric representation of meaning — so the knowledge base finds what you mean, even when the words differ. Through the same gateway as all your other AI traffic, so with the same grip.

Who it’s for

IT & platform teams

Want semantic search without operating a separate vector stack: no extra database, no standalone embedding service outside the platform.

Knowledge & information managers

Want people to find what is meant — including in large, Dutch-language document collections where keywords fall short.

Finance & procurement

Don’t want embedding cost as an invisible extra: reported separately, per model, apart from chat usage.

The problem

Embeddings are usually invisible — technically and financially.

Semantic search requires every document to be converted into embeddings. In most AI tools that happens out of sight: a separate service, a separate bill, and usage that never lands in your reporting. Large document collections make that painful — tens of thousands of documents means tens of thousands of calls.

In Numaga, embeddings run through the same gateway as the rest of your AI traffic. They fall under the same management, storage sits in the platform’s managed database, and usage is reported separately — not mixed with chat, because the volumes and cost are fundamentally different.

How it works

From document to findable answer.

Automatic with every knowledge-base sync — without separate vector infrastructure.

01

Documents become embeddings

On every knowledge-base sync and every upload, the platform converts the content into embeddings via an embedding model on the gateway.

02

Stored inside the platform

The vectors live in your environment’s managed database — single-tenant, in the Netherlands, with no separate vector stack to maintain.

03

Search by meaning and exact terms

Questions are answered hybrid: semantically (meaning) combined with exact terms — important for names, codes and domain jargon.

04

Usage reported separately

Embedding traffic has its own overview: which models, how many calls and what it costs — apart from chat usage, so your reporting stays clean.

Make your documents findable by meaning.

We show how embeddings work in your environment — from knowledge-base sync to the cost overview.

Get demo access