About

We're building the research workspace we wished existed.

Atlaslab is a small team of clinicians, scientists, and engineers based in Shanghai. We got tired of switching between five tools just to finish one analysis. So we built one workspace where an AI agent can actually open your files, run your code, and write your report — and we kept your data on your machine, where it belongs.

Why we built it

Research tools should remove busywork, not add it.

01 The pain

The problem we kept hitting

A clinical question becomes a literature review, a cohort table, a regression, a figure, a draft, and a paper. Each step uses different software. AI tools live in browser tabs that can't actually touch the files. Hours disappear copying things between windows.

02 The product

What we wanted instead

A single desktop workspace where the agent reads your PDFs, runs your R script, plots your figure, drafts the manuscript section, and tracks every result back to its source — so a reviewer or collaborator can audit any conclusion.

03 The user

Who we make it for

Clinicians running retrospective studies. Wet-lab teams processing -omics data. PhD students fighting their dissertation. Hospitals running internal research. Anyone whose work has to be reproducible and verifiable — not just impressive.

What we believe

Four principles we won't compromise on.

Local first

Files stay on your machine. We don't index them, we don't ship them anywhere. The agent only sees a file when you ask it to read one.

Every result is traceable

The Data Flow graph links every chart, table, and number back to its source file and the tool call that produced it. Nothing is "just trust the AI."

Curated, not chaotic

Official Skills and Tools are reviewed for clinical, bioinformatics, and writing workflows. You install them in one click; they update through the Market.

No hype, no fake numbers

We won't claim "5,000 researchers" or "99.9% accuracy" until they're true. We're a young team. We ship what works, we fix what doesn't, we tell you when we don't know.

Get in touch

Questions, feedback, or a pilot to discuss?