Note: We make Atlas. This is a comparison written by the team that built it, not a neutral third-party review. Where Roam Research has the better answer for a given research job, the article says so plainly. See the table rows where Roam Research wins and the "When to choose Roam Research" section below. The goal is to give you the data you need to choose the right tool for the kind of work in front of you, not to convince you Atlas is the answer to every research job.

Atlas is a visual research workspace for people whose work depends on understanding a body of papers: a thesis, a treatment decision, a major-purchase teardown, a literature review. Roam Research is a networked-thought outliner: bullet-based notes with bidirectional links, block-references, daily notes, and a graph view across all pages, the original tool of the networked-personal knowledge management category. Both tools touch a researcher's daily work, the wedge is what happens after the first answer. Atlas deconstructs each paper into a Knowledge Map (a visual map of the argument), projects a whole corpus into a Semantic Map, runs every answer through claim-source-justification (the citation-grounded surface that explains why a passage supports a claim), and compounds prior work into a persistent knowledge graph so projects get smarter the longer you use Atlas. Roam's brand and the networked-thought paradigm are genuinely battle-tested, the bidirectional-link and block-reference design defined the personal knowledge management category and remains widely used by power users. If you need to trust the answers (for a thesis, a treatment plan, a brief, a hire), the visual maps, claim-source-justification, and compounding graph are where Atlas earns the comparison.

How is Atlas different?

Roam Research and Atlas overlap at the surface: both touch the work of reading and reasoning over sources. But they diverge on three capabilities that decide whether the output is shareable, defensible work. This section walks through the three differences, in order.

1. Visual maps of every paper and project

Atlas builds two kinds of visual map automatically as you read. A Knowledge Map deconstructs each paper into its argument structure: claims, evidence, definitions, and labeled relations between them (motivates, causes, enables, contradicts), laid out as a multi-level zoom. You see the paper's spine at the top level and drop into the supporting passages with a click. A Semantic Map projects your whole project (sources, notes, chats, citations) into a spatial canvas where related items cluster by topic, and you can re-project the same canvas under a new topic angle without re-reading anything. The Semantic Map is how 200 papers stop being a folder and start being a corpus.

"It's like an ultimate GPT. I can finally see what I've read." Kyle Lao, NUS researcher

Roam Research does not have a per-paper claim-evidence deconstruction or a topic-angle re-projection across an entire project. If you've ever spent an afternoon trying to recover the structure of a paper you read three weeks ago, the Knowledge Map is the surface that pays for itself first. Visual maps make a body of papers legible at a glance, and the multi-level zoom of the Knowledge Map is the surface Atlas is built around.

2. Every claim traces to a source, and Atlas explains why the source supports it

The hallucination problem in AI research tools isn't "the model made something up." It's "the model put a citation next to a claim that the cited passage doesn't justify." Atlas renders every answer as a claim-source-justification triple: the claim, the passage, and a one-sentence explanation of why the passage supports the claim. You can click into the source paragraph and read the highlighted sentences in context.

The benchmark Atlas runs internally is the H/V ratio: the proportion of generated sentences whose citation does not survive a passage-level re-check, divided by the proportion that does. Atlas targets H/V < 0.1 on the citation-grounding benchmark, and we publish how the benchmark is constructed in Verifiable AI Research (2026): What It Actually Means. Roam Research's answers may include citations or links to sources, but they're grounded at the sentence-citation level (or not at all), not at the claim-justification level. For most casual question-answering the gap doesn't matter. For a thesis sentence, a legal brief paragraph, or a treatment-decision summary, it does. The wedge in one sentence: every claim traces to its source, and Atlas explains why the source justifies it.

3. Your projects compound: the second month is 10× the first

Roam Research treats each session (or project, or workspace) as a separable container: work goes in, an answer comes out, and the next session starts fresh. Atlas builds a persistent per-user knowledge graph across projects: every citation you jump to, every annotation you make, every Knowledge Map and Semantic Map you generate accumulates into a four-layer graph (citations + mentions + KMs + SMs) that the next chat can draw from. Open a new project on a related topic and Atlas can pull in the relevant sources, prior annotations, and chat history without re-ingesting.

This is the capability we hear about most from long-term users: the second month is 10× the first because the graph has something to work with. John Tan, a postdoc using Atlas for a multi-year literature review, describes it as "the only tool where the work I did last semester is still doing work for me this semester." Put plainly: projects get smarter the longer you use Atlas. Roam Research does not have an equivalent persistent compounding graph across projects, which is the wedge for sustained, multi-month research.

Try Atlas: Sign up for an evaluation sample (10 sources · 5 lifetime AI chats) and run a Knowledge Map on one of your own papers. Used by researchers at NUS, NTU, SMU, and eight other universities.

Comparing Atlas and Roam Research

Both Atlas and Roam Research touch a researcher's daily work, but they live in different categories. Atlas spans paper deconstruction, project navigation, source-cited AI answers, and compounding context across a research corpus, Roam spans networked-thought outliner personal knowledge management with bidirectional links and block-references. Roam's integration with the networked-thought paradigm is broader as a general personal knowledge management substrate, Atlas's research depth at the citation surface is deeper. The rest of this article walks through the five capability surfaces where the two tools differ: per-paper deconstruction, project-level navigation, source-cited answering, literature-grounded annotations, and compounding context across projects. Each section is a two-column table where every row is a real capability, and at least one row in each table is one where Roam Research wins or ties.

Paper deconstruction (Knowledge Map)

The Knowledge Map is Atlas's per-paper surface. It deconstructs a single paper into a multi-level argument structure with labeled relations between claims, faithful-to-source nodes (the node text comes from the paper, not from a generated summary), and hierarchical breadcrumbs that let you read down from the high-level thesis to a specific paragraph.

Good to know: The bottom row belongs to Roam Research. Atlas does not ship that surface. The Knowledge Map's payoff is recovering a paper's argument three weeks after you first read it, when topic chips alone are no longer enough.

Project / corpus view (Semantic Map)

The Semantic Map is Atlas's per-project surface. It projects all the sources, notes, chats, and citations in a project into a spatial embedding where related items cluster by topic. Re-project the same canvas under a different topic angle without re-ingesting anything.

Good to know: Roam Research's strength on that row is genuine. If your work depends on it, that's the boundary. The Semantic Map's payoff is when 200 papers stop being a folder and start being a corpus you can re-project under different topic angles without re-reading.

Citation-grounded answers

Atlas produces claim-source-justification triples: the claim, the passage, and a one-sentence explanation of why the passage supports the claim. You can jump to the source paragraph, read the highlighted sentences, and check whether the reasoning holds.

Good to know: Both tools have a citation surface, the wedge is whether the surface explains why a passage justifies a claim, not just which passage was cited. For everyday Q&A the gap is invisible, for a thesis sentence or a brief paragraph it's the whole game.

Literature-grounded annotations

Atlas auto-annotates each paper on ingest. Citations inside the paper become first-class objects: Atlas resolves the cited source (when open-access), pulls the relevant passage, and lets you see how a citation in the paper builds up its argument across multiple sources without leaving the document.

Good to know: Literature-Grounded Annotations resolve citations inside the paper you're reading. When a paper cites a source that's open-access, Atlas pulls in the cited passage. It is not a web-grounding feature, it is a way to see how a single paper builds its argument across the sources it cites.

Compounding context across projects

Atlas builds a four-layer persistent graph (citations + mentions + KMs + SMs) across all your projects, so chats, annotations, and maps from one project become context for the next.

Good to know: Compounding is the slowest capability to demonstrate in a demo and the biggest payoff in week eight. If your work is many small, unrelated projects, Roam Research's session-isolated design is the right choice, isolation is a feature, not a gap. Compounding pays off for sustained, multi-month research.

Price comparison

Atlas is a paid product. There is no perpetual no-cost plan, you get a short evaluation sample (10 sources · 5 lifetime AI chats), and after that you pay $20/mo or $204/yr for Atlas Pro. At the paid tier, Atlas is the only tool with Knowledge Map, Semantic Map, claim-source-justification, and compounding graph. You aren't paying for chat tokens, you're paying for capabilities that Roam Research doesn't have at any tier.

When to choose Atlas vs Roam Research

• Want paper structure deconstructed multi-level? Go with Atlas. (Knowledge Map)
• Want answers that explain how each citation justifies the claim? Go with Atlas. (claim-source-justification)
• Want your projects to compound over months? Go with Atlas. (4-layer graph)
• Want a networked-thought outliner with bidirectional links and block-references? Go with Roam Research.
• Tied: capturing networked thoughts in a daily-notes workflow**: both work fine, Roam designed for that exact pattern. The wedge only opens up once you're building a corpus you'll return to.

Recommendations by user type

• PhD researchers: Atlas. Lit-review-heavy years 1–2 benefit most from the Knowledge Map (deconstruct each paper without re-reading). Thesis-writing years 3–4 benefit from claim-source-justification (every thesis sentence anchored to a passage). Roam Research works for one-off tasks, the multi-year compounding graph is what makes Atlas the right tool here.
• Students doing literature reviews and thesis research: Atlas, scoped to research workflows (dissertation, thesis, literature review). The Knowledge Map is the largest time-saver in the lit-review phase, and the compounding graph keeps prior work accessible across semesters.
• Knowledge workers (consultants, analysts, PMs, journalists): Atlas when reading PDFs and citing them is the core work, Roam when networked-thought outliner personal knowledge management is the daily need.
• Personal researchers with stakes (medical, legal, major-purchase, deep autodidact): Atlas. Burst-usage research where the stakes are high (medical, legal, major-purchase, deep autodidact) is exactly where citation-grounded reasoning earns its keep. Roam Research is a fine starting tool, Atlas is the tool you graduate to once you realize you'll need to defend the answer.

The honest one-liner across all four segments: if the research compounds, Atlas is the bet, if each session is self-contained and the next one starts fresh, Roam Research's form is genuinely the better fit, and we'll say so plainly. The expensive mistake is using a session-isolated tool for compounding work (every project pays the re-ingestion tax) or using a corpus tool for one-off questions where simpler tools are faster. A useful diagnostic: ask whether you expect to come back to the same corpus in three months. If yes, the project-graph approach carries its weight, if no, lighter tools win on friction. Most research workflows we hear from at universities (Cambridge, Harvard, MIT, Stanford) sit firmly on the "yes" side: the corpus is the same corpus across semesters, advisors, and grant cycles, which is the cohort Atlas is built for. The corollary is that picking the right tool is mostly a question about your work pattern, not a question about which feature list is longer, both tools do their job well within the form they're built for.

Migrating from Roam to Atlas

Roam Research is built around three primitives that decide what migration looks like: pages (titled documents made of nested bullets), blocks (the individual bullets, each with a permanent block UID), and bidirectional links (the [[wikilink]] and ((block-ref)) syntax that wires the graph together). On top of that sit daily notes (one page per day, your default capture surface), the graph view (a force-directed render of every page-to-page link), and Roam's query language (a datalog-flavored DSL that filters blocks by attribute, page, or tag). Exports come in three flavors: EDN (the full datomic-style graph with all block UIDs, references, and metadata), JSON (the same graph in a more tractable shape), and Markdown (one file per page, blocks rendered as nested bullets, page links as [[wikilinks]], block references typically inlined as the referenced text).

The pragmatic path into Atlas is the Markdown export. Atlas's bulk import takes .md files directly: open the import dialog, select your exported folder, and each Roam page becomes an Atlas note inside the project you choose. What migrates cleanly: page bodies (your prose and bulleted content survive as nested markdown), the page-to-page link text (the [[wikilink]] syntax is preserved as text inside the note), block content rendered as flat indented bullets, and any PDFs you reference (re-upload them as sources so Atlas can run a Knowledge Map against the paper itself).

What does not survive the round-trip: block-reference transclusion (((block-uid)) collapses to the inlined text it was pointing at, so the live two-way reference is gone), Roam's query blocks (the datalog queries are not portable and would not have anywhere to run inside Atlas in any case), sidebar layout and per-page right-sidebar state, custom roam/js plugins and CSS, and the datalog-style attribute pairs you may have used for structured data inside bullets. The graph itself does not migrate as a graph, Atlas's organising primitives are project, source, Knowledge Map, and the four-layer compounding graph across projects, not freeform bidirectional blocks. The honest framing: you keep the prose and the reading list, you lose the block-ref topology. For most researchers the prose plus the underlying PDFs is the part that matters, the topology was a working surface, not the artefact. If your Roam graph is mostly daily-notes journaling and outliner thinking, keep Roam for that and use Atlas for the dedicated research corpus. If your Roam graph is mostly per-paper notes and reading lists, the markdown route lands you in Atlas with the substance intact and you re-build the structure inside Knowledge Maps, which is the surface that pays back the migration cost first.

A worked example: literature-review section from 8 papers

Concrete scenario: you have eight papers on a single sub-topic (say, transformer interpretability via sparse autoencoders), and you owe a literature-review section that synthesises them into a few hundred words with citations. Here is what the two workflows look like end to end.

In Roam, the typical pattern is one page per paper, each page populated with nested bullets you write as you read. You skim each paper, capture claims as bullets, tag them with #claim or #evidence, and link them to thematic pages with [[wikilinks]] like [[sparse autoencoder]] or [[feature direction]]. Block references let you transclude a specific bullet from paper A into a synthesis page that sits alongside paper B's matching bullet. When you sit down to write the section, you open a new page, pull up the linked references in the sidebar, and assemble the paragraph by hand from the bullets you wrote. The work is real and the result reflects your reading. The cost is also real: the structure is whatever you remembered to capture, the bidirectional links are only as good as the tags you laid down, and three weeks later if you forgot to tag a key claim with [[sparse autoencoder]] it sits orphaned in its paper's page.

In Atlas, the same eight papers go into a project as sources. Atlas auto-generates a Knowledge Map per paper on ingest: each paper's claims, evidence, definitions, and labeled relations (motivates, causes, enables, contradicts) become a multi-level argument structure with node text drawn faithfully from the source. The Semantic Map projects all eight papers into a spatial canvas where related claims cluster by topic, you re-project under "feature decomposition" or "training dynamics" without re-reading. When you ask Atlas to draft the literature-review section, every sentence comes back as a claim-source-justification triple: the claim, the passage from one of the eight papers, and a one-sentence explanation of why that passage justifies the claim. You click into the source paragraph, read the highlighted sentences in the original PDF, and accept or rewrite. Literature-Grounded Annotations resolve the open-access citations inside each paper, so when paper 3 cites paper 7's Theorem 2 you see how the argument builds up across the corpus without uploading anything extra. The work you do is editorial rather than archaeological, you spend your attention on whether the synthesis is right, not on whether you remembered to tag every block. Two months later when a related sub-topic opens, the four-layer compounding graph means the eight papers, their Knowledge Maps, and the chat threads you ran against them are already in scope for the new project, you do not re-ingest, you extend.

When Roam is the right call

Roam Research is the better answer for several research patterns, and the honest version of this article names them directly. First: block-reference-first outliner workflows. If your thinking happens as nested bullets and you rely on ((block-ref)) to transclude the same atomic thought into multiple contexts, that is a working pattern Atlas does not replicate. Atlas's primitives are project, source, note, and Knowledge Map, not freeform blocks with stable UIDs. If you have spent years building muscle memory around the outliner, the migration cost is not worth the citation surface for jobs where the bullets themselves are the artefact.

Second: daily-notes-driven personal knowledge work. Roam's daily-notes page is the original of its category and a genuinely good capture surface for journaling, fleeting notes, meeting minutes, and quick links you want to come back to. Atlas does not have a daily-notes primitive and is not trying to. If your day starts in Roam's daily note and that is where your thinking lives, keep it there.

Third: queries over blocks. Roam's datalog query language lets you ask structural questions about your graph ("show me every block tagged #claim on a page linked to [[interpretability]]") that have no equivalent in Atlas. If you have built a workflow around Roam queries, that is a real capability you would lose.

Fourth: legacy Roam users with established graphs. If you have years of Roam content and the graph already works for you, the right move is usually to keep Roam for what it does and add Atlas only for the dedicated research corpus where claim-source-justification matters.

Common objections and edge cases

"I want bidirectional links inside Atlas the way Roam has them." Atlas does not ship freeform [[wikilink]] and ((block-ref)) primitives, and adding them would not be a feature gap fix, it would be a different product. The compounding graph Atlas does build is structurally different: citations, mentions, Knowledge Maps, and Semantic Maps accumulate per user across projects, and the next chat draws from that graph without you laying down the links by hand. If the bidirectional-link surface is the thing you most want from a tool, Roam remains the right call and we will not pretend otherwise.

"Can I keep Roam for daily notes and use Atlas for the research corpus?" Yes, and this is the most common stack we hear from researchers who keep both. Roam captures the daily-notes and outliner thinking, Atlas hosts the source library, the per-paper Knowledge Maps, the cited-answer chat, and the compounding graph across projects. There is no live integration between the two, so anything you want in both places has to be exported and re-imported, but the workflows do not conflict and the cognitive split (capture in Roam, deconstruct in Atlas) is clean.

"What happens to my block references if I migrate the markdown export into Atlas?" Roam's ((block-uid)) transclusions resolve to the inlined text of the referenced block during the markdown export, so what lands in Atlas is the content of the bullet you were referencing, not a live pointer back to its source block. The page-to-page [[wikilink]] syntax is preserved as text inside the note. The practical implication: you keep the prose and the reading list intact, and you rebuild the structural surface inside Atlas using Knowledge Maps per paper and the Semantic Map across the corpus, which is where the citation-grounding payoff lives anyway.