How it works - One product, three things worth understanding.

Laminae does three things. Deployment is your call. Ingestion happens in buckets. Retrieval is hybrid and source-attributed.

The three things to understand

Deployment

Managed cloud · Self-hosted · Air-gapped

Managed cloud, self-hosted, or air-gapped — same product, your call

Run Laminae as a managed per-tenant deployment, or take the same Docker Compose stack and run it on your own infrastructure. The wedge is open-standard, so the choice never locks you in.

Air-gapped works the same way the connected version does — bundled Ollama replaces the cloud model endpoints, and nothing leaves your network. There's no separate edition; it's the same code path.

Buckets and MCPs

Ingestion · MCP server · Bring your own AI client

Upload to a bucket, expose it as an MCP server, done

Buckets are managed, vectorised knowledge stores. MCP servers are how your AI client talks to them. Non-technical teams can spin up both in an afternoon — no data team required.

Any MCP-compatible client connects: Claude Desktop, Cursor, Continue, an internal Copilot. Laminae returns evidence — the AI client generates the answer. You bring your own AI.

Agentic retrieval

Hybrid retrieval · Re-ranking · Provenance

Hybrid retrieval, source-attributed, no summarising layer

Dense plus sparse plus re-ranked. Every chunk is returned with its source document, page, and snippet, so the AI client — and the human reading along — can always verify the answer.

There is no narrative-generation step in the middle. Laminae returns evidence; the AI client decides what to do with it. That's why source attribution actually means something here.

Where teams benefit from Laminae

  • Professional services
  • Financial services
  • Healthcare
  • Regulated manufacturing
  • Customer support
  • Legal
  • Insurance
  • B2B SaaS

Want to see Laminae on your own documents?

Based and hosted in

  • Frankfurt
    Frankfurt am Main
    Germany