Némos vs Roam Research in 2026 — Bidirectional Links vs On-Device Capture

Roam Research is the app that started the modern PKM era. When it launched in 2019, the combination of bidirectional links, the daily notes page, block references, and the graph view created a new genre — call it networked thought or graph-based notes. Every PKM app shipped since (Logseq, Obsidian, Reflect, Capacities, Tana) owes its mental model to Roam. The product was valued at $200M at its 2020 peak and built one of the most evangelical user communities in software.

The cultural moment passed. Roam's pricing ($15/mo, $165/year) stayed steep while competitors caught up and shipped offline modes, mobile apps, and better performance. The web app remains the canonical experience and it's still slow on large graphs.

Némos doesn't try to be Roam. We're a capture-first second brain — built for the moments Roam was never optimized for: phones, watches, voice, screenshots, in-the-moment thoughts. Here's how the two tools actually compare in 2026.

What Roam invented

Roam's contribution to PKM is hard to overstate. Before Roam, bidirectional links existed in academic tools (Niklas Luhmann's Zettelkasten, TheBrain) but weren't mainstream. After Roam, every serious note app shipped them. Block references — the ability to embed a single block in multiple pages and edit it in one place — was also a Roam original.

The daily notes page is another Roam contribution. Every day gets a note. Anything you write that day lives there by default. Links emerge naturally because today's note references yesterday's. Over years, the graph builds itself.

For users who internalized this workflow, no other tool feels right. Logseq, Reflect, and Obsidian all replicated the pattern, but Roam users often say the original still has the cleanest implementation of block references.

Where Roam lost the thread

Three structural problems sit underneath Roam in 2026.

First, the mobile experience. Roam is a web app wrapped in a mobile shell. On modern iPhones with 5G, it's still slow — initial load can take 3-5 seconds, and the keyboard interaction has constant lag. For in-the-moment capture, this is fatal. A tool that takes 5 seconds to be ready loses to a tool that's ready in 500ms.

Second, pricing. $15/mo or $165/year is the highest in the PKM category. Roam's pitch was that it was a tool for serious thinkers worth the price; competitors have largely caught up at $5-10/mo with better mobile experiences.

Third, pace. Roam's development slowed significantly after 2022. Roam Depot (the plugin ecosystem) launched but never matured to Obsidian's level. Roam AI is still in beta in 2026. The product feels frozen.

What Némos offers Roam refugees

If you've been a Roam user for 3+ years and are looking around, Némos solves a specific problem: capture on phones and watches that Roam was never built for.

• Apple Watch complication for instant voice capture (Roam has no Watch presence).
• Screenshot auto-import with OCR so anything you screenshot on iPhone lands in your library searchable (Roam needs manual upload).
• On-device AI in 100-300ms versus Roam's cloud round-trip on a slow connection.
• Free tier versus Roam's $165/year minimum.

The trade-off is the linking ethos. Némos doesn't have bidirectional links as a first-class primitive. We do basic note linking, but we don't have block references, the graph view, or auto-daily-notes. If those are central to your work, Roam (or its open-source competitors) is the right tool.

How they fit together

A practical workflow for committed Roam users: capture in Némos on mobile, synthesize in Roam on desktop. Voice memos, screenshots, and quick ideas land in Némos via the Watch or iPhone. During desktop sessions, the captures get exported (manually or via copy-paste) into Roam where you can link them and embed them into your existing graph.

The slight friction of moving between two systems is offset by gaining a mobile capture experience that Roam can't deliver natively.

Where Némos wins on its own

For users who never bought into the bidirectional-link ethos in the first place — and many people legitimately don't — Némos is the simpler answer. You capture, you search, AI surfaces things, and you don't need to think about how everything connects to everything else.

Some users find Roam's linking discipline produces real insight over years. Others find it adds maintenance overhead without proportional payoff. If you're in the second camp, Roam was probably the wrong tool for you anyway; Némos's flat-but-searchable model is more honest about how most knowledge work actually happens.

Privacy reality

Roam is cloud-only. Every page, every block, every query crosses Roam's servers. Roam AI uses OpenAI. The privacy posture is unremarkable — comparable to Notion or Mem.

Némos has zero cloud surface beyond iCloud (E2E encrypted). For users with privacy constraints, Roam doesn't compete.

Real-world workflow comparison

A 36-year-old strategy consultant uses Roam as her daily thinking environment. Every morning the daily notes page opens and she captures meeting prep, client observations, and idea fragments. She wikilinks every client (Acme, Bolt, Cresco) and every concept (pricing-power, channel-conflict, retention-spike) so the graph builds itself across months. The unlinked-references feature surfaces accidental mentions she didn't explicitly link, which occasionally produces real insight. Block references let her quote a specific paragraph from June 8th into today's client memo without copy-paste. This is the workflow Roam invented and still does best.

The same consultant captures heavily on her iPhone during travel. She screenshots a competitor's investor deck on a plane, records a voice memo about a client intuition while walking from her hotel, saves a long FT article at midnight, and jots an Apple Watch reminder for a follow-up call. Roam's iOS app is functional but slow, doesn't OCR screenshots, doesn't transcribe voice memos, and has no Apple Watch presence. The Mobile sync occasionally produces conflicts that require manual resolution on the desktop.

Némos captures all four into one indexed library with on-device OCR, real-time voice transcription, parsed article text, and watch capture. When she searches "competitor pricing retention article" three weeks later, all four artifacts surface. Roam returns only blocks already linked into the graph.

Most heavy Roam users we talk to use Némos for mobile capture and Roam for desktop synthesis. The two products complement.

The privacy deep-dive

Roam's data path: every block, every page, every query crosses Roam's backend on AWS. Roam AI features call OpenAI's GPT-4 API with block contents serialized as context. Roam retains operational logs and stores backups. The privacy policy is reasonable but the surface area is real, and Roam's enterprise security posture has had public stumbles over the years that some users still cite.

Némos's data path: notes, screenshots, voice memos, and articles are stored locally in MMKV. iCloud sync (if enabled) uses CloudKit with Advanced Data Protection. AI runs on Apple's on-device Foundation Models via the Neural Engine. There is no third-party LLM.

What happens on a long flight

Roam is partially functional offline. The web app caches recently-viewed pages but sync conflicts on reconnect are not rare. AI features fail offline. New block references can be created but the graph view may not refresh until you reconnect.

Némos runs identically online and offline. Voice memos transcribe. Screenshots OCR. Semantic search hits a local index. Apple Watch capture relays via Bluetooth. iCloud sync queues encrypted deltas for landing.

The hidden costs nobody mentions

Roam's $15/month or $165/year is the visible cost. The hidden costs are significant. First, the learning curve is steep — most users invest 20-40 hours before they reach productive workflows, and many give up before reaching them. Second, the bidirectional-link discipline has to be maintained or the graph decays into noise. Third, the product roadmap has been criticized as inconsistent, with long quiet periods followed by feature bursts. Fourth, the export options preserve content but flatten block references in a way that other tools can't fully import.

Némos has hidden costs too. No bidirectional links. No graph view. No daily notes page. We trade graph richness for capture speed.

Migration friction (a real timeline)

Week one: export your Roam graph as JSON or Markdown via Settings → Export. The Markdown export preserves wikilinks but flattens block references. Install Némos. Drop the Markdown bundle into Némos via the share extension — each page becomes a searchable note.

Week two: keep Roam running for daily notes. Add Némos captures during the day for screenshots, voice memos, and articles. Note which Roam features you actually use weekly.

Week three: assess whether Némos's retrieval covers your synthesis needs.

Week four: cancel Roam if your usage is mostly capture + retrieval. Keep Roam if you genuinely use bidirectional linking for synthesis.

Total switching cost: roughly seven hours across the month.

What Apple users specifically gain

Némos was built iPhone-first. Roam was built web-first. The Action Button on iPhone 15 Pro and later starts a Némos voice capture in under one second. The Apple Watch app captures from the wrist. Live Activities pin recording state to the Dynamic Island. Spotlight indexes Némos system-wide. iCloud sync uses Advanced Data Protection. Foundation Models on iOS 26+ run on the Neural Engine. AppIntents expose your library to Siri Shortcuts. None of this surface exists on Roam.