Note: We make Atlas. This is a comparison written by the team that built it, not a neutral third-party review. Where Saga has the better answer for a given research job, the article says so plainly. See the table rows where Saga wins and the "When to choose Saga" 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. Saga is a workspace tool combining notes, tasks, and AI features: pages, tasks, references, and an AI assistant integrated across pages with a clean, fast interface. 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. Saga's brand, design, and integration of tasks with notes are genuinely well-executed, the page editor is fast, the AI assistant is integrated cleanly, and the workspace style is a clean alternative to Notion. 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?

Saga 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

Saga 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. Saga'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

Saga 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. Saga 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 Saga

Both Atlas and Saga 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, Saga spans pages plus tasks plus AI in a unified workspace. Saga's integration of notes with tasks is broader as a general workspace, 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 Saga 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 Saga. 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: Saga'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, Saga'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 Saga doesn't have at any tier.

When to choose Atlas vs Saga

• 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 unified workspace with notes, tasks, and AI in one tool? Go with Saga.
• Tied: keeping a workspace of notes and tasks with light AI assistance**: both work fine, different jobs. 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). Saga 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 and citing papers is the core work, Saga when a unified notes-plus-tasks workspace 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. Saga 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, Saga'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 Saga to Atlas

If you've been keeping research notes in Saga and want to move the work into Atlas, the migration is more workable than it sounds because Saga exports as markdown and Atlas ingests PDFs and pages as first-class objects. The practical sequence is: pick the Saga pages you actually want to bring (most users find that's a smaller subset than the full workspace), export them as markdown, and upload them to Atlas along with any underlying PDFs you originally stored in Saga or kept alongside it. The PDFs are the part that matters most for Atlas's research surfaces: each one gets deconstructed into a Knowledge Map on ingest, and the citations inside each paper become first-class objects that resolve to cited sources when those sources are open-access.

What migrates cleanly: page body content (prose, lists, headings), the basic structural hierarchy of your notes, and the underlying source PDFs you kept. What does not migrate: Saga's auto-linked references between pages (Atlas's graph is built around citations, mentions, Knowledge Maps, and Semantic Maps rather than backlinks between user-authored pages, so the bidirectional-link surface is not the same shape on either side), Saga's AI chat history (Atlas's AI conversations are project-scoped and bound to the citation-grounded surface, so prior Saga chats don't import as runnable history), workspace-level permissions and sharing settings (Atlas's permissions model is its own), and tasks (Atlas does not have task management, which is genuinely well-executed in Saga, if you want to keep the task workflow, keep Saga running for that).

A reasonable migration path for a research-heavy user: keep Saga running for the daily workspace and tasks for a few weeks, while you upload the actual research corpus (the PDFs and the long-form notes) into Atlas and let the Knowledge Maps, Semantic Map, and compounding graph form. Once Atlas has the corpus and the citation-grounded surface is doing the work you used to do in Saga, you can decide whether to retire Saga or keep both. There is no integration between the two tools, so sources have to be uploaded to each separately, but the workflows do not conflict and many researchers run them in parallel for the first month while the Atlas graph builds up. The single mistake to avoid is trying to one-shot the move: export everything, dump it all into Atlas, and expect the graph to be useful on day one. The compounding payoff is on the order of weeks, not minutes, that's the form of the tool, and rushing it gives a misleading first impression.

A worked example: literature-review section from 8 papers

Concretely: you have eight papers you've gathered for a literature-review section of a thesis chapter, and you need to produce a tight 800-word synthesis with defensible citations. Two workflows, side by side.

In Saga, the path is roughly: create a workspace page per paper, drop the PDF embed or a manual summary into each page, link related pages with Saga's auto-linked references, and ask the AI assistant to help draft the synthesis on a new page. The links between pages give you a navigable structure, and the AI assistant can pull context from across the pages it can see. The bottleneck is the manual summarization step (you're the one reading and abstracting), and the citation surface in the final draft is whatever the AI assistant produces, which is typically a sentence-level citation rather than a passage-level reasoning trace. For a low-stakes literature-review section, that's enough.

In Atlas, the path is: upload all eight PDFs into one project. Each paper is auto-deconstructed into a Knowledge Map (claims, evidence, definitions, labeled relations), so you can see the spine of each argument without re-reading the full paper. The Semantic Map projects all eight papers as a spatial canvas where related claims cluster: you can re-project the canvas under the topic angle of your literature-review section (say, "methods used across these eight papers" or "common limitations") without re-ingesting. You then run the synthesis as a project chat, and every sentence in the generated draft is rendered as a claim-source-justification triple: the claim, the passage from the specific paper, and a one-sentence explanation of why the passage supports the claim. You can click into each cited paragraph and verify the reasoning. Literature-Grounded Annotations also resolve citations inside each paper, so when paper #3 cites a foundational source that's open-access, Atlas pulls in the cited passage and you can see how the argument builds across the sources the paper itself draws on.

The differences that decide the comparison: in Saga, you do the deconstruction (the per-paper summarization), and the synthesis is grounded at the page-citation level. In Atlas, the deconstruction is done for you (Knowledge Map per paper), the corpus view is a re-projectable spatial canvas (Semantic Map), and the synthesis is grounded at the claim-justification level with the reasoning trace attached. For a thesis chapter you'll defend at a viva, that reasoning trace is the surface you'll actually use when an examiner asks "and what in the cited paper justifies that sentence?", Atlas hands you the highlighted passage and the one-line justification, Saga hands you the page link. Both are useful surfaces, the one you want depends on whether the answer needs to be defensible.

When Saga is the right call

There are workflows where Saga is the better recommendation and we'll say so plainly. Small-team collaborative wikis with AI assistance are where Saga's design earns its keep: the unified pages-plus-tasks-plus-AI workspace, the clean editor, and the auto-linked references between pages make it a good shared knowledge base for a small team that wants AI help drafting and searching across its own notes. Atlas is not a team wiki, it's a research workspace. Auto-linked references across pages as the primary navigation surface (the Roam/Notion-style bidirectional-link experience) is something Saga ships and Atlas does not, because Atlas's graph is built around citations, mentions, Knowledge Maps, and Semantic Maps rather than user-authored backlinks. If your work pattern depends on backlinks-as-architecture, Saga is the right form. Lightweight project docs (briefs, meeting notes, project plans, decision logs) are exactly the kind of content Saga handles cleanly and Atlas is not designed for, trying to use Atlas as a general doc tool will feel heavyweight. Real-time collaborative editing for non-research docs (multiple people editing the same page at once, comments, suggestions, the standard collaborative-doc workflow) is where Saga's workspace genealogy shows up positively. Atlas's collaboration surface is built around shared research projects (sources, annotations, maps), not around real-time multi-cursor editing of arbitrary pages. If you need three teammates editing a launch brief together at 4pm, use Saga. If you need three teammates reasoning over the same 60 papers across four months, use Atlas.

Common objections and edge cases

"I already use Notion / Obsidian / Roam for notes. Do I need Saga or Atlas?" If the notes tool is doing what you need, keep it. Atlas isn't a notes tool, it's a research workspace for papers, citations, and the reasoning over them. The question is whether you have a research corpus that justifies a dedicated tool. If you read and cite papers regularly (thesis, treatment plans, briefs, structured teardowns), Atlas earns its keep alongside your notes tool. If your work is mostly text-first knowledge work that doesn't depend on a paper corpus, Saga or your existing notes tool is the cleaner choice.

"Can I use Atlas without committing to the full compounding graph?" Yes. The evaluation sample (10 sources, 5 lifetime AI chats) lets you run a Knowledge Map on a paper and a project chat on a small corpus without any subscription decision. The compounding graph is what makes Atlas pay off in week eight, but the per-paper Knowledge Map and the claim-source-justification surface are useful on day one. The honest test: ingest one paper you know well, look at the Knowledge Map, and ask a question that requires a specific passage. If the answer renders with the reasoning trace and you can click into the source, you have the wedge.

"What if my corpus is mostly non-PDF (web pages, transcripts, internal docs)?" Atlas is opinionated toward PDFs and the citation surface inside them. Web pages and transcripts can be uploaded, but the Knowledge Map and Literature-Grounded Annotations are most valuable on properly structured papers with reference lists. If your corpus is entirely web content with no underlying paper structure, Saga's general-page model is a closer match. The threshold is whether your sources have arguments-with-citations you'd want to deconstruct, if yes, Atlas, if no, Saga.