A native Logseq
for macOS
An outliner that edits the Markdown on your disk — nothing in between. Journal, backlinks, instant search and Git, in a SwiftUI app that opens before you finish the keystroke. No Electron. No cloud. No lock-in.
Free forever · Apple Silicon · Intel build · Release notes
Everything Logseq does.
Nothing Electron needs.
Written from scratch for macOS. Not a port, not a wrapper — an app that behaves like it belongs on the machine.
Files are the truth
Plain .md with CommonMark and wikilinks. No database, no index, no proprietary layer. What you see is what is on disk — open it in any editor, diff it in any tool.
Search without an index
Full text, backlinks, unlinked references and page names, all through a Rust ripgrep FFI that greps the files each time. Nothing to rebuild, nothing to go stale.
Git is the sync layer
Embedded libgit2: auto-commit on save, push/pull to any remote, branch switching, conflict resolution, commit history with inline diffs, and revert down to a single file.
Outliner, keyboard first
Indent, collapse, multi-select, drag to reorder across pages. Every edit has a symmetric inverse, so undo and redo never drift. Bracket pairs, checkboxes and tags come along.
⌘K and ⌘F
One palette for pages, slash commands, favorites and recents. One find bar that reaches across every journal day, loaded or not. Both keep up with your typing.
Full frame rate, any vault
Recycled rows drawn directly with CoreText, absolute-frame layout, no per-frame SwiftUI solve. A five-thousand-page journal flings as smoothly as an empty one.
Coming from somewhere else? SeqLog vs Logseq · SeqLog vs Obsidian
Less software, more writing.
Four decisions made once, then defended in every commit since.
The file is the source of truth
Markdown is the only data store. No SQLite, no cache, no intermediate model to fall out of sync. Edit a note in Vim and the app agrees with you.
No index, ever
Search greps the vault directly. No background indexing, no first-run wait, no corrupt database to delete when things go strange. Point at a folder and write.
Apple native, all the way down
SwiftUI, AppKit and Swift Concurrency — with CoreText taking over the hot path where SwiftUI could not hold the frame. No cross-platform layer to apologise for.
Your sync, your server
Version control you already know, instead of a cloud you have to trust. Auto-commit captures every edit; push and pull move it between machines. Nothing routes through us.
A short dependency list.
Every entry here had to earn its place, and can be pointed at when something breaks.
- Interface
- SwiftUI + AppKit, CoreText-drawn rows
- Storage
- Plain Markdown files, no database
- Search
- Rust over C FFI, ripgrep engine
- Versioning
- libgit2, embedded — no
gitbinary - Language
- Swift 6.2, strict concurrency
- Tests
- 1,465 unit & UI tests
- Updates
- Sparkle, signed and notarized
- Requires
- macOS 15+, Apple Silicon or Intel
The four questions
everyone asks.
Is SeqLog open source?
No. It is free forever on macOS, for personal and commercial use, but the application source is not published. If open source is a requirement, Logseq and Obsidian's ecosystem are better answers — see the Logseq comparison.
Does it use a database?
No. Plain Markdown files are the only data store — no SQLite, no cache, no search index. Search greps the files on every query through a Rust ripgrep FFI, so there is nothing to rebuild and nothing to go stale.
Can Claude Code or a script edit my vault?
Yes. The vault is a folder of .md files, so anything that reads and
writes files can work on your notes. SeqLog watches the folder and picks up
external edits.
Can it open my existing Logseq graph?
Yes. Same layout — pages/ and journals/ — and it reads
Logseq's YYYY_MM_DD journal filenames alongside its own. Nothing is
converted or imported, so both apps can point at the same folder.
Start writing, not waiting.
Download it, point it at a folder, go. Free forever on macOS — no account, no trial, no upsell.
macOS 15+ · Apple Silicon · Intel build