a Obsidian
alternative,
honestly.
A second brain for you, forever. Knowledge base that works on top of a local folder of plain text files.
what Obsidian got right.
We're not here to bash. Obsidian earned its users by nailing things outl stands on the shoulders of.
- ✓ Plain markdown on disk, no metadata pollution. Total interop with any markdown tool.
- ✓ Massive plugin ecosystem: over a thousand community plugins for almost anything.
- ✓ Strong [[wiki-links]] and a polished graph view.
- ✓ Free for personal use, with a mature mobile app.
where it breaks for an outliner power-user.
It's a prose editor, not an outliner.
Bullets are just markdown bullets. There's no block-level addressability without plugins, no first-class slash command for blocks, no built-in outliner mode. Power users install the Outliner plugin, but fold-state, drag-handles and keyboard chords are added on top rather than built in.
Built-in sync is a paid subscription.
Obsidian's built-in sync is a paid subscription, and the algorithm isn't publicly documented in detail, so outl can't speak to its failure modes. You can self-host with git or Syncthing instead, though those tools don't resolve outline-level conflicts specifically. outl's sync is peer-to-peer over iroh by default, end-to-end encrypted, free, with the merge algorithm open source and auditable.
Closed source.
Free for personal use, but the source is private. You can't read, audit, fork or self-host. If the company changes direction, your notes stay in a format that only their binary fully understands.
Electron desktop runtime.
Desktop runs on Electron, which bundles a browser engine with the app. For an app that's mostly editing text, that's a heavier runtime than a native binary.
you want to move 80 bullets from page A to page B.
In an outliner built around blocks, this is select-and-move. In Obsidian by default it's cut, paste, fix the indent, and check that nothing referenced those blocks. The Outliner plugin helps with chords, but block references can still break because Obsidian tracks them as ^block-id text anchors in markdown rather than as nodes. Move the anchor and a [[page#^id]] link pointing at it can break silently.
outl is built as an outliner from line one. Blocks are nodes in a tree. Moves preserve references because IDs are stable in the sidecar, the markdown you see is just the rendering.
Obsidian vs outl
| feature | Obsidian | outl |
|---|---|---|
| open source | ✕ | MIT |
| clean markdown (no UUIDs) | ✓ | ✓ |
| sync via tree-CRDT merge | ✕ | ✓ |
| built-in sync without an account | ✕ account required | ✓ device-to-device, E2E (relay sees metadata) |
| desktop app | ✓ | beta (macOS, Linux, Windows) |
| code blocks that execute | via plugin | ✓ python, js, lua, rust |
| TUI / terminal editor | ✕ | ✓ vim keys + slash commands |
Checked on 2026-11-07. Code execution on mobile covers Python, JS and Lua, not Rust.
coming from Obsidian?
one command.
Your Obsidian vault is already plain markdown. Just
outl init
on the vault directory — outl reads your .md files as-is. Backlinks
and [[wiki-links]] resolve automatically. Block references via the
outliner-plugin syntax can be reconciled with a follow-up
outl doctor
run.
And one thing Obsidian doesn't do: outl ships an MCP server so Claude, Cursor and ChatGPT can read and write the same notes over MCP, no copy-paste. outl itself uploads nothing, the tool you connect sends what it reads to its own model provider.