← statichum.studio

Self-Hosted Obsidian Sync Server That Obsidian Users Would Pay for Today

dev tool real project •• multiple requests

Obsidian's own Sync service is cloud-only, and the power-user community has been asking for years for an official license to run the same sync backend on their own server. HN comments as recent as April 2026 explicitly state users would pay if Obsidian offered a self-host tier. Current workarounds (the community plugin obsidian-livesync on CouchDB, Syncthing, iCloud folder hacks) all break in subtle ways... conflict resolution is the actual hard part and each workaround implements a slightly different wrong answer. Opportunity: a paid self-host-compatible sync product, either official if Obsidian blesses it or as a community competitor that nails CRDT-style conflict resolution for markdown + file attachments.

builder note

Don't wait for Obsidian to bless you. Ship a paid plugin plus a self-host server image, nail conflict resolution with Y.js or Automerge, and price it $50 one-time plus $5/month optional hosting. The users will tell Obsidian about you... then either Obsidian acquires you or competes with you, and both outcomes are fine.

landscape (6 existing solutions)

The ask is narrow and the user population is deep-pocketed (Obsidian paid-sync subscribers are the self-selected 'I already pay for my notes' group). A CRDT-backed markdown-aware sync server with an Obsidian plugin client, priced as a one-time license plus optional hosted tier, walks into an existing revenue stream. The technical moat is conflict resolution for Obsidian's specific metadata and attachment model... Syncthing-level generic file sync is not enough.

Obsidian Sync (official, cloud-only) $10/month end-to-end encrypted, only option blessed by Obsidian... only works against Obsidian's servers.
obsidian-livesync (community plugin) Runs against CouchDB self-hosted. Works but has sharp edges on conflict resolution, attachments, and multi-device bootstrap. Power-user tier only.
Syncthing Great file sync, no understanding of markdown or Obsidian's metadata. Concurrent edits produce 'conflict' copies that a human has to resolve.
Git + mobile-git apps Works for single-user disciplined sync. Mobile ergonomics are rough, conflict merging is manual, and attachments blow up repo size.
iCloud Drive / OneDrive / Dropbox folders Most popular DIY. Silent corruption on concurrent edits, attachment sync lag, and no CRDT-style merges. Obsidian warns against it.
Logseq Sync / Anytype Adjacent products. Users who care about self-host sometimes jump to Logseq or Anytype... but that's leaving Obsidian, not fixing it.

sources (3)

hn https://news.ycombinator.com/item?id=47759415 "I'd pay for the option to host my own server" 2026-04-13
hn https://news.ycombinator.com/item?id=47729694 "Obsidian discussion with sync cost complaints" 2026-04-08
other https://www.aitooldiscovery.com/guides/obsidian-reddit "sync cost is the top complaint in Obsidian reviews" 2026-02-20
obsidianself-hostedsynccrdtnotes