Némos vs Heptabase in 2026 — Visual Whiteboard vs On-Device Capture

Heptabase started as a researcher's tool: take your notes, scatter them on infinite whiteboards, arrange them visually, and let connections emerge from spatial layout rather than rigid hierarchy. Five years later, it's the best visual PKM tool on the market — used heavily by PhD students, designers, and anyone whose thinking is fundamentally non-linear. The founder Alan Chan has been transparent about the product philosophy in long-form essays, which built unusual trust among power users.

The whiteboard is the killer feature. You can drop cards (notes), highlight key passages, draw connections, and group ideas in clusters. Cards are full notes underneath the whiteboard surface, so you're not flattening to a mind-map; you're laying out your library spatially.

Némos doesn't compete on visual layout. We're a capture-first second brain — optimized for the moment ideas land, with on-device AI handling search and retrieval. The two tools serve different points in the knowledge workflow. Here's how to figure out which one fits.

Why Heptabase exists

Most note apps assume thinking is linear: write something, save it, find it later. Heptabase assumes thinking is spatial: you arrange ideas on a whiteboard, see how they relate, cluster them, draw lines between them, and the layout itself becomes part of the meaning.

For some kinds of work, this is exactly right. Writing a thesis chapter, designing a product architecture, planning a multi-part essay, mapping a research domain — all benefit from being able to see all the pieces at once and rearrange them visually.

Heptabase nails this. The whiteboard is fluid, cards are full editable notes (not just labels), PDF highlights land directly on the canvas, and the cross-references between boards keep the graph navigable.

What Heptabase doesn't do well

Heptabase is built for the synthesis layer — where you've already gathered material and now you're arranging it. It's less strong at the capture layer — the moment when you see something interesting and need to save it in under a second before it evaporates.

The iOS app has been the weaker surface for most of Heptabase's life. It's better in 2026 than it was in 2023, but it's still designed as a companion to the desktop experience. No Apple Watch app, no native screenshot capture, no voice-first flow. If your capture happens primarily on a phone or watch, Heptabase will frustrate you.

What Némos does instead

Némos is the capture layer. The Action Button starts a recording. Screenshots auto-OCR. Apple Watch complication is one tap. On-device AI tags, categorizes, and indexes everything for semantic search.

What Némos doesn't do: spatial layout. We don't have a whiteboard. If you tried to write a thesis or design a complex system in Némos, you'd hit the wall at synthesis — there's no canvas to lay out your sources and see them connected.

How they fit together

For researchers and writers, the natural workflow is Némos upstream, Heptabase downstream:

1. Capture in Némos throughout the day: voice memos on walks, screenshots of papers, highlights from articles, ideas blurted into your Watch.

2. Synthesize in Heptabase during dedicated thinking blocks: open a whiteboard for the project you're working on, pull in the relevant captures from Némos (manual copy or export), arrange them, and write the actual output.

This is the same pattern as Day One + Némos or Reflect + Némos: each tool nails its specialty and the slight overlap is fine.

Where Némos competes head-to-head

For non-researchers, Némos can replace Heptabase entirely. If your "knowledge work" is closer to "remembering useful things across the day" than "synthesizing a long project," you don't need the whiteboard. Némos's free tier covers the capture-and-retrieval workflow without the $9-15/mo Heptabase requires.

If your work *is* synthesis-heavy (writing long-form, designing complex systems, doing academic research), Heptabase remains worth the price. Némos won't replace the whiteboard.

Privacy considerations

Heptabase is cloud-only. Notes and whiteboards sync via Heptabase's servers. Heptabase AI uses OpenAI under the hood. The privacy posture is comparable to Mem or Capacities — strong policies, real cloud surface.

Némos has zero cloud surface beyond iCloud (E2E encrypted). For users with privacy constraints, Heptabase doesn't compete; Némos is the only credible option.

Pricing reality

Heptabase is $8.99/mo on the annual plan or $14.99/mo monthly. No free tier — you get a 7-day trial.

Némos is $0/mo for the full capture experience or $4.99/mo for Pro. Over a year, Heptabase costs $108-180; Némos costs $0-60. The gap is substantial, especially because most Némos users don't need to upgrade.

The trade-off is real: if you need the whiteboard, Heptabase's price is justified. If you don't, Némos delivers more capture value at a fraction of the cost.

Real-world workflow comparison

A 27-year-old PhD candidate in cognitive psychology uses Heptabase as her thesis-writing environment. She has six whiteboards open — one per chapter — and each whiteboard contains 80-200 cards. Each card is a note: a quotation from a paper, a methodology sketch, a hypothesis, an empirical finding. She arranges cards spatially so related ideas cluster visually. When she writes a section, she pulls relevant cards from the whiteboard into a draft, watches the connections form visually, and produces prose that reflects the underlying structure she built. This is the workflow Heptabase was engineered for, and it's the best tool on the market for visual research synthesis.

The same PhD candidate captures heavily during the workday on her iPhone. She photographs whiteboard diagrams from advisor meetings, records voice memos about emerging hypotheses while walking between buildings, saves PsyArXiv preprints at midnight for later reading, and jots quick Apple Watch reminders about edits. Heptabase's iOS app exists but is significantly slower than the desktop apps, doesn't OCR photographs, doesn't transcribe voice memos, and has no Apple Watch presence.

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 "advisor whiteboard hypothesis preprint" three weeks later, all four artifacts surface. Heptabase returns only cards already placed on a whiteboard because that's what Heptabase indexes.

Most heavy Heptabase users we talk to use Némos for capture and Heptabase for synthesis. The two products complement rather than compete.

The privacy deep-dive

Heptabase's data path: every card, every whiteboard, every connection crosses Heptabase's backend on AWS. Heptabase AI features call OpenAI's GPT-4 API with card contents serialized as context. Heptabase retains operational logs. The privacy policy is reasonable — no training on user content, standard retention windows — but the surface area includes Heptabase, AWS, and OpenAI. For confidential research with embargoed findings or pre-publication data, the surface area matters.

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. For academic confidentiality, Némos is the structurally easier choice.

What happens on a long flight

Heptabase works partially offline. The desktop app caches recently-viewed whiteboards and lets you create new cards. Sync resumes on reconnect. AI features fail offline. The mobile app is more limited. New whiteboard creation works offline; AI-driven card suggestions don't.

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

The hidden costs nobody mentions

Heptabase's $108-180/year is the visible cost. The hidden costs add up. First, the whiteboard model encourages large card counts; users with 5,000+ cards across 30+ whiteboards report performance degradation in the desktop app. Second, the spatial arrangement is sensitive to screen size — whiteboards that look organized on a 27-inch display can feel cramped on a laptop. Third, the AI features are an add-on. Fourth, the export options preserve card content but flatten the visual layout, which means leaving Heptabase loses the spatial structure that made the library useful.

Némos has hidden costs too. No whiteboard. No spatial canvas. If your thinking is fundamentally visual, Némos doesn't replace Heptabase.

Migration friction (a real timeline)

Week one: export your Heptabase library as Markdown. The export preserves card contents but loses whiteboard layout. Install Némos. Drop the Markdown bundle into Némos via the share extension — each card becomes a searchable note with tags preserved.

Week two: keep Heptabase running for whiteboard-driven synthesis. Add Némos captures during the workday for screenshots, voice memos, and articles. Note which Heptabase whiteboards you actually use weekly.

Week three: assess whether Némos's flat retrieval can replace the whiteboard view for your workflow. For most knowledge workers it can. For genuine visual thinkers, Heptabase remains the better tool.

Week four: keep both or migrate selectively. Total switching cost: roughly six hours across the month.

What Apple users specifically gain

Némos was built iPhone-first. Heptabase was built desktop-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 Heptabase. Apple users who pick Heptabase get a strong desktop product and a thin mobile one.