Ask a question of your documents and get an answer you can check. Every citation opens the passage it came from, and when nothing in the project answers, TraceLab says so instead of guessing.
Research piles up in documents, interviews and old decisions. When a question comes back, finding something that sounds right is easy. Knowing what the material actually supports is the work.
How it works
1
Add your documents.
Upload them to a project. TraceLab parses them, then splits and indexes them for search.
2
Ask, then check.
Read the answer beside the passages it cites. Each citation opens the passage it came from, in a document that still exists.
3
Keep what you found.
Capture findings and notes as evidence, including what contradicts you and what you’ve ruled out, then turn the work into a report you can export.
When search isn’t enough
Queue a DeepSearch run for a question that needs more than retrieval. Preview what it will do, watch its progress, and promote the finished report into the project. Collections let you gather passages and synthesize them.
From your assistant
The MCP adapter gives Claude Code, Claude Desktop, Codex or any stdio client the same work: ask, search, capture evidence, run DeepSearch and build reports. It signs in through your browser, and deletes stay in the web app.
Two ways to start
Use it yourself.
TraceLab accounts are by invitation. Ask us for one, then add your documents. To work from an assistant, install the MCP adapter from npm; it needs Node 18+. TraceLab and DeepSearch are open source under MIT on GitHub, so you can run them with your own keys.
TraceLab shows you what an answer is built on. It doesn’t make the answer right. The adapter is MIT-licensed, and the service needs a TraceLab account.