About - Built for the teams the AI hype cycle keeps missing

Laminae exists because the companies that would benefit most from retrieval-augmented AI — teams that are data-rich but IT-light — keep getting handed tools designed for someone else.

Founded by David Bunting and based in Frankfurt am Main, Laminae is a focused team building a single product: a knowledge layer that turns your documents into source-attributed evidence any MCP-compatible AI client can use, stored in focused, relevant spaces to avoid information drift. No chat UI to retrain your team on. No SDK to wrap. No data lake to maintain.

We chose Germany deliberately. European data protection norms aren't a marketing veneer here — they're the default. If your compliance team needs the whole stack to run inside your own network, that's a supported deployment, not a special edition.

Standard (MCP)
Open
First-class, not a tier
Self-host
Built in, hosted in
Germany

Approach - How Laminae thinks about retrieval

Three commitments shape every product decision: be precise, be trustworthy, be relevant. They're also why Laminae looks unfamiliar next to most AI startups.

  • Evidence, not narrative. Laminae returns the chunks; your AI client writes the answer. We don't insert a summarising layer in the middle, because that layer is where provenance quietly dies.
  • Open standard, not vendor wrapper. MCP is the interface. Any MCP-compatible client connects without an SDK or a custom integration. If we go away tomorrow, your data and your tooling are still yours.
  • Self-host as default-shaped. The cloud product is the same Docker Compose stack we ship to self-hosted customers. Air-gapped works the same way. There's no second-class deployment.

Principles - The five things we won’t compromise on

These aren't taglines — they're the constraints that decide what makes it into the product and what doesn't.

  • Source-attributed by default. Every retrieved chunk carries the document, page, and snippet it came from. If the chain breaks, the answer doesn't ship.
  • No telemetry from the product. The product doesn't phone home. What you do with your buckets and your MCP servers is your business — not ours, and not our cloud provider's.
  • Encryption at rest, BYOK on request. Cloud tenants get per-tenant encryption keys. Bring your own keys if your compliance team requires it. Air-gapped tenants never touch our infrastructure at all.
  • Size Agnostic. Laminae is built for organisations of rall sizes. Ever company needs a reliable knowledge layer lean enough that ops can ship the first bucket in an afternoon.
  • No chat UI. We don't ship a chat surface. The AI client your team already uses is better than anything we'd build — our job is to make it smarter.
  • No wasted tokens. Embeddings happen once, on ingest. Retrieval sends only the chunks that answer the question, not the whole document. The cost story is supposed to get better as your team uses the system more, not worse.

From the blog

Notes on retrieval, MCP, and the parts of enterprise AI we keep arguing about — from the team building Laminae.

Why a smaller information surface gets you better answers

Vector databases reward scope. Pour everything into one giant index and unrelated documents start bleeding into every search — the answers come back confidently mixing facts from places you never asked about. One bucket per concept is the fix.

Read more

The most expensive way to use AI is to drag your PDF in every time

The default pattern — drop the document into the chat, ask the question, repeat tomorrow — costs you twice. Once in tokens spent re-embedding the same text. Again in answer quality, when the document outgrows the context window. There is a cheaper way.

Read more

Want to see Laminae on your own documents?

Based and hosted in

  • Frankfurt
    Frankfurt am Main
    Germany