Last updated: August 16, 2026
What enterprise grounding requires
Isolation, authorization, freshness, and auditability—on the path that actually calls the model.
A retriever that leaks Customer A’s files to Customer B is a failed system. Keep the corpus in your tenant: your search index, your MCP tools, your app. Kimss governs the hop to the model—auth, kill switch, tool allowlist, and governed requests—without becoming a second knowledge lake.
The pattern
Retrieve locally, then send grounded messages through Kimss.
- Your application retrieves relevant chunks from your own store.
- You include those chunks in the prompt / messages you send to Kimss.
- Hermis routes that payload plus attached MCP tool schemas. It does not query pgvector or generate embeddings for knowledge.
POST /v1/files/upload remains for ephemeral model attachments, not a knowledge base. Former Studio Data, File Search, /api/v1/rag/documents, and /v1/vector_stores/* return HTTP 410.
Governance around the model hop
Grounded traffic should inherit the same gateway controls as completions—auth, governed requests, and attribution.
If retrieval bypasses your approved identity path, you reintroduce Shadow AI for documents. Keep ingest in your systems; keep model calls on Kimss. Combine with /multi-tenant-ai-security and /ai-agent-security.
Where to implement
Start with the customer docs, then validate in a non-production workspace before customer data.
Engineers: /docs/data_assets and /docs/creating_agents. Security reviewers: /trust. Evaluators comparing platforms: /compare.
Frequently asked questions
Does Kimss host a vector database?
No. Kimss does not ingest documents, generate RAG embeddings, or query pgvector. Retrieve on your side and send augmented messages through the gateway.
What happened to Data Assets and File Search?
Those surfaces are removed. Public RAG and vector-store APIs return HTTP 410. See /docs/data_assets and /docs/agentic_rag.
How should agents ground answers?
Your application retrieves chunks from your own index or MCP tools, then includes that context in the messages you send to Kimss.
Where is quick start?
/docs/quick_start and /app/signup.