Should you just use Syncthing?

Plenty of people should. Syncthing is excellent, open source and free, and a lot of Obsidian users already run it. The one difference that decides it is architectural, and it shows up the moment a phone is involved.

Download the bundle Deployment guide

Syncthing deserves better than a comparison written to lose. It is one of the most respected projects in self-hosting — around 89,000 stars, released under MPL-2.0, actively maintained, and trusted by people who trust almost nothing. This page is written by the people who give away the alternative, so read the last section accordingly.

The one difference that decides it#

Syncthing is peer-to-peer. There is no server in the middle; devices talk to each other directly. Its own documentation puts the consequence plainly: it "exchanges your data across your machines as soon as they are online at the same time."

A sync server is the thing in the middle. It is always on, so every device syncs against it whenever that device happens to be awake, and nothing waits for anything else.

For two desktops that are both on most of the day, that difference barely matters. For a laptop and a phone, it is the whole question. Edit a note on your phone on the train, close the app, and open the laptop at home: with Syncthing, the change only moves if both were reachable at some point in between. With a server, the phone pushed it the moment you made it.

Where Syncthing is the better choice#

Where a server is the better fit for an Obsidian vault#

The honest middle: Syncthing with an always-on node#

Most experienced Syncthing users already solved the "online at the same time" problem, by adding a device that never sleeps — a NAS, a Pi, a small VPS — running Syncthing as one more peer. Every other device syncs with that one, and it behaves a lot like a server.

That closes most of the gap. If you already run that setup and it works, this page is not an argument for switching. What it does not give you is the browser access, the per-device partial sync, or the history in one place — but you may not need any of those.

When two devices disagree#

Both keep the losing version rather than throwing it away, which is the part that matters most:

One thing is true of both and worth doing either way: keep .obsidian out of sync, or at least .obsidian/plugins/*/data.json and workspace.json. Those files are rewritten in the background, and they conflict silently.

The part you should weigh against us#

We give the server away because we sell an Obsidian task-manager plugin, and a server you can run yourself makes "your data is yours" a checkable claim. So we have a reason to want you here rather than on Syncthing.

The counterweight is that the plugin's free tier is a complete sync client — you can run this server for years and never pay us — and that Syncthing is genuinely good. If you are already happy on Syncthing, stay. If a phone keeps missing your changes, you now know why.