The compliance case for self-hosting your knowledge layer
Legal teams keep asking the same three questions about retrieval-augmented AI. From a Frankfurt-based view of the EU AI Act and GDPR, here's what the answers look like when the knowledge layer runs on your own infrastructure.
by David Bunting, Founder
1. Where does the data actually live?
This is the first question every legal team asks, and the one most retrieval products fudge. Embeddings are still your data — reconstructing the source text from them is easier than most people assume, and getting easier. Chunks are definitely your data. Query logs are your data. If any of those leave the building, the answer to “where does it live” is no longer your network.
Self-hosting collapses the question. With Laminae running inside your own infrastructure, the embeddings, the chunks, and the query logs all stay there. Air-gapped goes a step further: bundled Ollama replaces the cloud model endpoints, so even the inference call doesn’t leave the network. It keeps GDPR mechanical, too — when an access or erasure request touches an ingested document, the chunks, embeddings, and query logs it concerns are rows in your own database, not a request into a vendor’s processor agreement.
Key dates
2. Can you trace an answer back to a document?
The second question, every time: if a regulator or a customer asks why your AI told them something, can you point to the source? A summarising retrieval layer breaks the chain here. Once an LLM has paraphrased the source, the citation is a claim, not a trace.
Laminae handles this by not summarising in the middle. Retrieval returns the chunks themselves — each one carrying its source document, page, and snippet — and the AI client uses them as evidence. The chain from “answer” to “exact span in exact document” stays intact, which is what an audit actually needs.
That’s also why the product doesn’t ship a chat surface. The AI client is the right place for the answer to be generated and cited; the knowledge layer is the right place for the evidence to come from. Mixing those concerns is what makes provenance brittle.
3. Who can you turn off, and how fast?
The third question is the operational one: if a control fails, can you cut access cleanly? With a SaaS knowledge product, “turning off” means filing a ticket and hoping the vendor responds quickly. With a self-hosted Laminae deployment, it means revoking a token on a bucket, or stopping a container.
Per-bucket auth helps here. Each bucket has its own access list and its own MCP endpoint, so a control failure in one domain doesn’t cascade to the others. You can rotate keys, retire a bucket, or pull an entire MCP server offline without touching anything else.
None of this is novel. It’s the same operational discipline that already applies to your databases and internal services. The only thing that’s changed is that retrieval now lives in that same operational layer, not in a vendor’s console where you can’t see it.