Obsidian Sync: Self-Hosted Server

Self-hosted LiveSync plugin

  1. vrtmrz/obsidian-livesync
    GitHub - vrtmrz/obsidian-livesync

Self-hosted LiveSync is a community-implemented synchronization plugin.


  • Visual conflict resolver included.
  • Bidirectional synchronization between devices nearly in real-time
  • You can use CouchDB or its compatibles like IBM Cloudant.
  • End-to-End encryption is supported.

How to use

  1. Setup IBM Cloudant
  2. (Fly.io)
  3. Setup your CouchDB
  1. obsidian-livesync/setup_own_server.md at main · vrtmrz/obsidian-livesync
    obsidian-livesync/setup_own_server.md at main · vrtmrz/obsidian-livesync · GitHub

Setup CouchDB to your server


Could Obsidian at least add support for file system browsing on IOS? I have a NAS mapped through the Files app that I keep my vaults on and would love to access that through the app

It’s not possible

It’s not that easy [Feature] Full File System Access For The iOS App (Open Existing Vault)

I don’t know if this is what you are after…I’m a newbie at this. But…
I have an Obsidian vault that I sync to a local server with FE File Explorer app. I think it’s called Owlfiles now. I can sync the Obsidian folders to my iPhone with FE File Explorer app on my phone and even edit the basic markdown files and resync and the changes will show up on my computer.

There isn’t much of an issue with trust because the notes are end-to-end encrypted. That is, the notes are stored on server encrypted and you have the key.

For personal use this is fine and in fact reassuring, but if the encryption is not at least auditable then there is still an issue of trust that makes this insufficient for many business environments.

You can use Nextcloud with WebDAV to remotely mount your files on android, use DAVx^5 to do that.

This might be a good use case for something like Amazon Machine Images.

This would let the obsidian developers charge a fee (perhaps $5/month) while allowing Obsidian to be run for users who want more storage, different availability profiles, or even on-prem capabilities with AWS Outposts, government cloud, or other private AWS cloud options.

I’m wary when I see the term “military grade encryption”.

The military grade is more a market thing at this point. We use the common aes256 and standard libraries.

I work in an offline environment, Having an enterprise option for a self-hosted sync server would be amazing. Bonus points if includes a way to host API’s for offline plugin management.

Firstly, I want to extend my appreciation for all the efforts put into making Obsidian such a powerful and versatile tool. It’s evident from the discussions above that the community highly values the ability to control their data and its storage.

I’d like to strongly advocate for a native self-hosted solution for Obsidian. While I understand that there might be complexities and challenges involved, the benefits, in my opinion, would be manifold:

Data Sovereignty: The ability to self-host ensures that users have complete control over their data. This is not just about trust; it’s about having the freedom and flexibility to manage our own data, especially in light of increasing data protection regulations globally.

Versatility: While many of us would use this feature for business purposes, as the conversations have highlighted, there are numerous use cases that stretch beyond the corporate realm. A one-size-fits-all approach might not cater to the diverse needs of the Obsidian community. Offering self-hosted solutions would allow everyone, from individual users to businesses, to tailor their Obsidian experience according to their unique needs.

Potential Revenue Stream: I, among many others, would be more than willing to pay for a native self-hosted solution, even if it carries an associated cost. This could serve as an additional revenue stream for Obsidian, ensuring that you are compensated for the effort and resources put into developing and maintaining this feature.

Reduced Server Load: As some members pointed out, allowing users to self-host could potentially reduce the load on Obsidian’s servers, leading to cost savings and improved performance for other services.

Attracting More Users: The addition of a self-hosted solution could attract a broader user base, especially those who prioritize data privacy and customization. This could further strengthen Obsidian’s position in the market.

Enhanced Trust: Offering users the choice to self-host could further solidify the trust in Obsidian. Even though the data is encrypted, having the option to manage our own data storage can add an extra layer of assurance for many users.

In conclusion, while I understand the hesitance and the potential challenges of implementing a native self-hosted solution, I genuinely believe that the benefits, both to the users and Obsidian as a platform, would be substantial. Let’s not limit this to just businesses or enterprises; every user, regardless of their intent, should have the option to choose where and how they store their data.

Have you looked at the Self-hosted LiveSync plugin mentioned several times above? It would appear to do pretty much everything you’re looking for, and it’s available now.

1 Like

Thanks for re-posting about the LiveSync plugin - I had missed it earlier in this thread and I will definitely check it out. I’ve had a few issues recently with the official sync, so it will be nice to have an option.

1 Like