a Roam Research
alternative,
honestly.
A note-taking tool for networked thought, bi-directional links, daily notes, block references.
what Roam Research got right.
We're not here to bash. Roam Research earned its users by nailing things outl stands on the shoulders of.
- ✓ Block-level addressability with
((uid))references: copy a thought once, see it everywhere. - ✓ Daily notes that anchor everything to a date by default.
- ✓ [[Wiki-links]] with automatic backlinks made the graph navigable.
- ✓ The UX of an outliner where every bullet is a first-class node.
where it breaks for an outliner power-user.
Your data lives on their servers.
Workspaces are stored in a central Roam database. Export gives you JSON, so getting your notes out depends on that export path staying available.
No real offline merge.
How Roam resolves concurrent edits when two devices have been offline isn't documented publicly, so that's not a claim outl can verify from the outside. outl's own merge algorithm is a tree-CRDT, designed not to silently drop edits when two devices have been offline.
Closed source, paid subscription.
You can't read the code. You can't host it. You can't fork it if the company pivots. You pay a recurring fee to write your own notes.
No interop with other markdown tools.
There's no .md on disk to open in VS Code, Obsidian or grep. The format is JSON in their database, export is a one-way street.
you edit on a flight.
You write 200 blocks on your laptop offline. Your phone has the same workspace open, you tap a single block to fix a typo. When you land, both devices try to sync. Roam doesn't publish how it resolves a clash like that, so you're trusting an undocumented process with your edits. There's no merge UI you can check against.
outl's merge algorithm is a tree-CRDT (Kleppmann et al. 2022) with a published correctness proof: it orders both edit streams by HLC and applies them deterministically, designed not to silently drop edits when two devices have been offline. Sync is peer-to-peer by default over iroh, end-to-end encrypted, with no account needed. Roam keeps your workspace in their cloud, outl keeps it on your devices and syncs device to device. On the same Wi-Fi, two devices find each other over mDNS and sync with no internet connection at all, a state Roam's cloud-round-trip sync cannot reach.
Roam Research vs outl
| feature | Roam Research | outl |
|---|---|---|
| open source | ✕ | MIT |
| clean markdown (no UUIDs) | n/a (no .md) | ✓ |
| 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 | ✕ | ✓ 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 Roam Research?
one command.
outl import roam ~/backup.json ~/notes And one thing Roam Research 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.