Local-first or hosted outliner: choose by the failure you care about

Pick a local-first outliner if the failure you fear most is a company, a server, or a network standing between you and your notes. Pick a hosted outliner if the failure you fear most is your work splitting apart: one copy on the laptop, another on the phone, an email you meant to file, a collaborator working from last week’s export.

Both models fail. They fail in different places, and the honest way to choose is to decide which failure you would rather manage.

listlis is a hosted outliner. Its tree lives on a server, which is what lets it take email, sync every open tab in real time, share a branch, and answer an AI assistant from anywhere. If your requirement is plain files on your own disk, this page will tell you so, and point you at the tools that do that well.

What the two words mean

Local-first means the authoritative copy of your notes sits on your device. The app reads and writes local storage, usually Markdown files or a local database, and sync is a layer added on top. Logseq’s file-based version and Obsidian are the familiar examples in the notes world. If the vendor disappears, the files are still in a folder you control.

Hosted means the authoritative copy sits on a server, and every device is a window onto it. Workflowy, Dynalist, and listlis work this way. Open the app on any machine, sign in, and the whole tree is there. If the vendor disappears, what you keep is whatever you exported.

Neither definition says anything about speed, privacy policy, or quality. Those vary inside each camp.

The failures, side by side

Failure	Local-first	Hosted
Vendor shuts down or changes pricing	Files stay on disk	You rely on your last export
No network	Works fully	Depends on the app’s offline support
Two devices edit the same note	Sync conflicts are yours to resolve	The server orders the edits
Capturing from email or other services	Usually needs a bridge or plugin	Can accept mail and webhooks directly
Sharing a branch with someone	Send a file or run a sync service	Share a link
An AI assistant reading your notes	Needs a local bridge on your machine	Can connect to a remote endpoint
Backups	You run them	The vendor runs them; you export too

Read the table by row, not by column count. One row that matters to you outweighs four that don’t.

When local-first is the right call

Choose local-first if any of these is a hard requirement:

• You must own the bytes. A compliance rule, a client contract, or plain conviction says the notes cannot live on someone else’s server.
• You work offline for long stretches. Flights, field work, or an unreliable connection where a hosted app would leave you reading a cached shell.
• Your notes are a file system. You edit them with other tools, keep them in git, or run scripts over the Markdown. The files are the product; the app is one editor among several.
• You’ve been burned by a shutdown before. That memory is a fair reason to keep the primary copy at home.

If that’s you, an outliner that writes plain Markdown files fits. Our guide to leaving Logseq covers the local options, and the Logseq OG vs database breakdown explains what changed for file-based users.

When hosted is the right call

Choose hosted if your notes have to meet the outside world:

• Capture comes from everywhere. Email, a browser clipper, an automation. A server can receive these while your laptop is closed.
• You switch devices all day. Phone in the morning, desktop at noon, a borrowed machine at night. A hosted tree has no sync step to forget and no conflict file to reconcile.
• Other people or agents need a view. A shared branch for a collaborator, a public link for a reader, an AI assistant that pulls project context. All of these need an address that’s reachable when your machine isn’t.
• You’d rather not run backups. A hosted service carries that burden. You should still export, but losing a laptop doesn’t lose the tree.

The price is trust. You’re betting the vendor keeps running and keeps your data safe, so the export path matters more here than anywhere else.

The question that settles it

Ask: where does new information enter, and who needs to read it?

If new information enters through your own keyboard and only you read it, local-first costs you almost nothing and buys you full ownership.

If information arrives by email, from the web, from a teammate, or from an assistant, and has to be readable on several devices and by other people, a local folder turns into a sync project. Hosted removes that project.

Most people know their answer the moment they phrase it this way.

Hedge either choice

Whichever model you pick, cover its weak side:

• Local-first: run a real backup, not just sync. Sync faithfully copies a deletion. Test a restore once.
• Hosted: export on a schedule, in a format another tool can open. OPML and Markdown are the two to look for. Before you commit, export a real branch and open it somewhere else. Our Workflowy alternatives guide treats export as a first-class test for exactly this reason.

How listlis handles the hosted side

listlis keeps the whole account as one nested tree on the server. That’s what pays for the hosted benefits:

• Capture without your laptop. Give a branch its own email address at lists.listlis.com. Forward a message there and it lands under that branch as a node, attachments included. The Chrome extension clips a page as readable Markdown into the branch you choose.
• Every window stays current. Edits stream to every open tab and device in real time. There’s no sync button.
• Share a branch. A public link shows one subtree, and nothing else in your account.
• AI that reaches the tree remotely. listlis runs a hosted MCP server, so Claude and other MCP clients can read and edit your outline after an OAuth sign-in. Nothing to install on your machine. The MCP outliners comparison puts that next to the local-bridge approach.
• Leave whenever you want. Export the entire tree as Markdown or OPML, or export any single branch. Export stays available on every account.

What it doesn’t do: store your notes as files on your disk. If that’s your requirement, take it seriously and choose a local-first tool.

Try the hosted side in five minutes

Open app.listlis.com and make a root for a real project. Press o to add a line, Tab to nest it, and type a few next actions. Mark one with ! to make it a todo. Then give the project an email address, forward a message that belongs to it, and watch it arrive in the tree. Open the same tree on your phone.

If that loop feels like relief, hosted fits how you work. If it feels like giving something up, trust that too. For more side-by-side reads, the comparison hub collects every guide.