A Logseq alternative for pages, not outlines
Same conviction — notes belong on your machine. Different shape: Locus writes in calm document pages instead of an endless outline, with nothing to configure and no conventions to learn first.
Logseq is what happens when outliner people build a local-first tool, and for networked, bullet-by-bullet thinking it's superb. But plenty of people discover their notes want to be documents — drafts with headings, projects with tables and to-dos, pages with a face — and fighting an outliner to write prose is its own kind of friction. Locus keeps the ownership story and changes the writing surface.
Locus vs. Logseq, honestly
| Locus | Logseq | |
|---|---|---|
| Notes stay local | Yes — readable JSON on your Mac | Yes — Markdown/Org files in a graph |
| Account required | Never | Never (sync is a paid add-on) |
| Writing model | Document pages built from blocks | Outliner — every line is a bullet |
| Backlinks | Yes, with surrounding context | Yes, plus block references & graph |
| Daily journal pages | No — pages when you want them | Yes, the default entry point |
| Setup before writing | None — open and type | Graph folder, then conventions to learn |
| App type | Native Swift (macOS) | Electron (cross-platform) |
| Open source | No | Yes — a real point for Logseq |
| Mobile apps | No — Mac only | Yes |
| Price | Free while in development | Free; paid sync |
Where Logseq wins, it really wins: open source, mobile apps, and block-level references. This page is for the prose-shaped refugees.
The feel of the switch
Pages open as documents, not bullet trees. Type / for structure when you want it — headings, to-dos, toggles, tables, code with syntax colors — and plain paragraphs when you don't. Markdown expands as you type, @-mentions link pages, and everything exports back to Markdown whenever you ask. The philosophy behind it is in local-first notes; if you're also comparing the other file-based heavyweight, the Obsidian comparison is next door.
Questions people ask
Isn't Logseq already local-first?+
Completely — Logseq's file-based, offline-first model is the real thing, and if outlining fits your brain it's excellent. The switch to Locus is about the writing shape: prose in documents rather than thoughts in bullets, with zero conventions to learn before the first sentence.
Can I import my Logseq graph?+
Your graph is already Markdown files — point File → Import at the folder and each becomes a page with native blocks. Outline indentation flattens into nested lists; block references ((like this)) arrive as plain text, since Locus links pages rather than individual bullets.
Does Locus have daily notes and a graph view?+
Neither, deliberately. Instead of a journal-first workflow there's menu-bar quick capture into an inbox you process when ready; instead of a graph, backlinks with the sentence around each mention — the part of the graph most people actually read.
Who should stay with Logseq?+
Outliner natives, block-reference power users, anyone who needs mobile, and anyone for whom open source is the deciding factor — Locus isn't open source, and we won't pretend that doesn't matter to some people.
Free while in development · macOS 14 or later