Nodes

Executive Summary

Nodes is a Mac writing app built around Markdown, linked notes, and a local library. Its graph makes relationships visible, while an optional local model generates descriptions and tag suggestions. It is a candidate for the minimalist Markdown Mac notes comparison, particularly for people who want connected notes without configuring a large workspace.^[1]

The consequential distinction is storage: ordinary Markdown files sit inside Nodes' app container, while relationships and search metadata live separately. Opening a single external file works through a different surface, Light Windows. Buyers should evaluate those two workflows separately before moving an existing collection.^[2][3]

---

Product Overview

The main workspace organizes notes through tags, links, and search. Double-bracket links connect ideas; graph and timeline views provide other ways into the collection. Full-text search remains available independently of AI processing.^[1]

A practical evaluation workflow

Start with a small, noncritical collection. Open a loose file in a Light Window, edit it, and save it to its existing location. Then import a copy into the workspace and compare the experience. This tests the difference between a document editor and a managed library without committing the original collection.^[3]

Next, create a few links and use literal search for an unusual word in a note. If evaluating Rosetta, generate descriptions for those same notes and try concept-based searches. Check which descriptions exist before interpreting a missing semantic result as a retrieval failure: the search system works from that intermediate representation.^[8]

Finally, export a note as Markdown and save a complete .nodes archive. Reopen the Markdown in another editor; review the archive import manifest and its Keep Both, Replace, and Skip choices. This is a suggested acceptance test based on the documented workflow, not a report of hands-on testing.^[7]

---

Technical Architecture

The editor component uses native AppKit and TextKit 2, with a SwiftUI bridge. The Swift package separates core editing from optional code-highlighting and LaTeX bridges. Its service interfaces let the host application resolve wiki links and embedded images. That is useful architectural evidence, but inspecting the component does not establish the behavior of every part of the closed application.^[10]

Library Markdown lives at ~/Library/Containers/com.nvm.nodes/Data/Documents/MarkdownFiles/; PDFs and images have sibling directories. Nodes maintains connections, tags, and its index separately. Export produces a portable copy, including one that can be placed in a cloud folder or Git repository. That documented export mechanism is not continuous synchronization with an arbitrary external vault.^[2]

AI behavior and controls

The background agent is disabled initially. A user selects a model and can run operations manually before enabling background review. The model catalog exposes memory, disk, and vision requirements; an unsuitable model can be unavailable on the current Mac. Image understanding requires a vision-capable model.^[9]

Release 2.0 separated descriptions, tags, and reminders into individually controlled passes. Reminders require a downloaded model rather than the built-in Apple Foundation Model; the Apple model requires macOS 26. Treat app compatibility and AI compatibility as different purchasing checks.^[11]

Recovery is separate from portability

Paid library snapshots capture content and the supporting database locally. They run daily while the application is open and before replacing imports or database upgrades; restoration sets the current library aside so the operation can be reversed. These recovery points remain on the same disk. They address bad edits or imports, not loss of the computer or drive. Keep a portable archive elsewhere for that failure mode.^[12]

---

Strengths

• A coherent local library. Writing, linking, and finding material share a single Mac application rather than requiring a hosted notes account.^[1]
• A separate loose-file workflow. Light Windows make occasional Markdown editing possible without importing every document.^[3]
• Inspectability at the editor layer. The published component exposes its rendering architecture and integration interfaces, although the wider application remains distinct.^[10]
• Explicit recovery mechanics. The snapshot documentation explains capture, restoration, and the same-device boundary instead of presenting recovery as unlimited protection.^[12]

---

Cautions

• Plain files do not imply interchangeable libraries. Copying Markdown preserves writing, but Nodes-specific relationships and metadata require attention when exporting or migrating.^[2][7]
• Semantic coverage is conditional. Generated descriptions underpin semantic retrieval. Evaluate the results on actual notes rather than assuming every document is immediately searchable by meaning.^[8]
• The demo has no automatic recovery points. Manual copies remain possible, but the included snapshot feature requires a paid library entitlement.^[5]
• Localization remains limited. The store lists English, and a reviewer requesting more interface languages received a developer response describing unfinished localization work.^[4]

---

What Developers Say

In a June 2026 App Store review, rmateu described a visually appealing and internally consistent app while disagreeing with some design choices. In August, X-AANI praised the app but requested more interface languages. These are individual user reactions, not independent performance or privacy tests. They suggest that the opinionated interface is worth trying before importing a large collection.^[4]

---

Pricing & Licensing

US prices and entitlements checked September 15, 2026:^[5]

The developer says pre-2.0 users retain the full entitlement. Local model downloads consume disk and memory; selecting a paid edition does not make every model suitable for every Mac.^[5][9] The separate MarkdownEngine package is Apache 2.0; that license should not be extended to the whole app.^[10][6]

---

Competitive Positioning

Readers comparing Nodes with Obsidian, FSNotes, or ZenNotes should start with their existing files. If an arbitrary shared folder must remain the authoritative library, test that requirement before judging typography or graph appearance. Nodes documents an app-owned library and a separate external-document editor; confusing those modes produces a poor fit even when both use Markdown.^[2][3]

For a new personal collection, the more relevant question is whether links, tags, and local descriptions improve retrieval enough to justify adopting its library model. A graph alone is not a reason to migrate. Try a representative set of notes, verify export, and compare the actual writing workflow with the alternatives in the category report.

---

Viability Assessment

The release history shows continuing work through version 2.0.3 in August 2026, including fixes for table-only documents and long-list editing. The July 2.0 release established paid editions. Those facts support current availability and maintenance, not a prediction about revenue, staffing, or indefinite support.^[11] Portable content reduces dependence on the app, but preserving metadata still requires a deliberate export and backup routine.

---

Bottom Line

Recommended for: Mac writers who want a focused connected library and are willing to evaluate optional local AI on their own notes.

Not recommended for: A workflow that requires every existing folder to become a live library without import, or assumes same-disk recovery protects against device loss.

Outlook: The promising part is the combination of native editing, local retrieval, and documented escape routes. Judge it through file round-trips and real retrieval tasks; this review did not benchmark the application or audit its privacy implementation.

---

Research by Ry Walker Research • methodology