A pile of sources, one document you can defend

Notebooks

Playable below - no signup

Put the tender, the contract and the three annexes in one place. Draft against them, and let every claim in your text point back at the page it came from — a NotebookLM-style workspace you can self-host, with your sources staying on your infrastructure.

Try it below

Live demo

A finished notebook, six sources deep

A tender response assembled from six documents. Read the draft, open the sources, and see how the chat cites them rather than paraphrasing from memory.

An invented tender, invented sources. The demo has no network access - nothing is uploaded, generated or stored.

How it goes

From six PDFs to something you would put your name on

Add the sources

PDF, DOCX, XLSX, CSV, Markdown, HTML, email, a URL, a Nextcloud folder

Everything the answer has to be true to, in one place. Extraction, chunking and de-duplication run as each source lands, so a 42-page tender and a two-page certificate are equally searchable a minute later.

Interrogate them

Which requirements are knock-out and which are scored?

The chat answers from those sources and nothing else, with numbered citations pointing at the document and the page. When the sources do not contain the answer it says so - which is the behaviour that makes the citations worth anything.

Write the thing

Draft next to the sources rather than in a separate tab, and export when it is done. Both stay in storage you control, and the conversation about them is encrypted under your own key.

A notebook is not a knowledge base

When to use which

A knowledge base is standing infrastructure: it answers questions across your whole corpus, for anyone you share it with, indefinitely. A notebook is a workspace with edges - these six documents, this deliverable, this deadline. Use a knowledge base for "what do our contracts say about notice periods". Use a notebook for "write our response to this tender". They share the same retrieval underneath, so neither is a lesser version of the other.

What comes out

Beyond the draft

Briefing, FAQ, mind map, data table

Generated from your sources when one of those shapes is more useful than prose.

Citations that survive editing

Claims stay linked to the document and page they came from, so a reviewer can check rather than trust.

Legal Studio, when it is a legal document

The same workspace with Dutch and European primary sources attached, and citation verification that flags an invented reference.

FAQ

Worth knowing

How is this different from a knowledge base?

A knowledge base answers questions across your whole corpus, indefinitely. A notebook is a workspace around a specific set of sources, with a document you are writing next to them. Same retrieval underneath.

Where do the citations come from?

From retrieval over the sources you added - hybrid vector and keyword search, reranked. If a claim has no source, the answer says so rather than filling the gap.

Can I get the document out?

Yes - export it, or keep working in it. Your sources stay in your own storage throughout, and so does the draft.

Which file types can I add?

PDF, Word, Excel, CSV, Markdown, HTML, plain text and email, plus a URL to crawl or a Nextcloud folder to connect.

Is it on the free tier?

No - notebooks are an Enterprise module. The demo above is the whole interface, so you can judge it before talking to anyone.

Stop rebuilding the same answer from the same six PDFs

Bring one tender or one contract set and see what the first draft looks like.