An AI assistant grounded in your lab’s papers, protocols, and NDI datasets. Every answer cites the exact passage it came from — paper, PDF, or session. Your corpus stays in your lab’s index. We don’t train on it, and answers never pull from the open web.
LabChat is deployed per lab — each lab gets its own index and URL. Setup usually takes about a day.

LabChat indexes your lab’s published papers, internal protocols, session metadata, and notebook entries — every document the lab actually generates. Answers come back in plain English, with a numbered citation behind every claim.
Every answer includes numbered citations to the specific paper, protocol PDF, or NDI dataset they came from. Answers only pull from your lab's index.
LabChat reads OpenMINDS metadata from your NDI Cloud workspace. Ask about sessions, species, stimulus parameters, QC results — and get answers from your actual data.
New lab members ask questions about protocols, methods, and past experiments — and get answers drawn from the lab's own work. Tribal knowledge becomes queryable.
LabChat surfaces every retrieved passage behind an answer, not just one. When a protocol was updated mid-cohort or a finding was revised, both versions show up so you can read them side-by-side.
LabChat reads your lab’s corpus and writes grounded, referenced responses. Numbers in superscript link to the exact paragraph in a paper, protocol PDF, or NDI dataset.

No model training, no fine-tuning. LabChat builds a private retrieval index from your lab’s corpus and uses it at query time.
Add your lab's papers, protocol PDFs, and connect your NDI Cloud workspace. We ingest the PDFs and index them alongside your datasets.
Type in plain English. LabChat searches your indexed corpus and retrieves the most relevant passages from your papers, protocols, and sessions.
Responses include numbered citations linking to specific sources. Share threads with collaborators, cite them in lab meetings, reference them later.
Each lab gets its own encryption keys, its own URL, and its own retrieval boundary — nothing crosses between labs.
Per-tenant encryption keys managed in AWS KMS with automatic rotation.
No cross-tenant retrieval. Your papers never appear in another lab's results.
Every question, retrieved passage, and answer is logged for your PI's review.
PHI-flagged documents stay inside your HIPAA boundary. Consent metadata surfaces at retrieval time.
LabChat is deployed per lab, on dedicated infrastructure. You send us your corpus, we ingest it and stand up your URL, you start asking questions. Setup is usually a day. The team-onboarding payoff is forever.
LabChat isn’t a self-serve sign-up — each deploy is configured against your lab’s corpus. Every inquiry gets a response within 1 business day.