Selfsync Cloud

Obsidian plugin for Selfsync Cloud, a hosted version of selfsync. It syncs your vault with no lost edits: automatic merges, conflict copies, deleted file recovery and file history. End-to-end encryption is always on.

Status: early release. The plugin is published on GitHub Releases and is not in the Obsidian community directory yet. All accounts are on the free plan.

If you would rather run the server yourself, use the open selfsync plugin instead; it needs no account.

Installation

1. Download main.js, manifest.json and styles.css from the latest release.
2. Put them into <your vault>/.obsidian/plugins/selfsync-cloud/.
3. In Obsidian, open Settings → Community plugins, turn off restricted mode if needed and enable Selfsync Cloud.

Works on desktop and mobile, Obsidian 1.13 or newer. Do not enable it together with the open selfsync plugin in the same vault.

Usage

First device. Open Settings → Selfsync Cloud, press Start syncing and pick a region (CIS or Europe): that is where the encrypted data lives. No email or password is needed: the account is created at once, the vault is encrypted and uploaded. A 24-word recovery phrase appears in the settings; write it down soon, it is the only way back into the account if your devices are lost. Until you mark it as written down, the plugin reminds you in the status bar.

More devices. On a connected device press Connect a device and scan the QR code with the new device’s camera: Obsidian opens, signs in and joins the same vault. Without a camera, type the code shown under the QR under Already have an account → Enter a code, then the recovery phrase (or the password, if you added one). Codes work once and expire after 10 minutes. The phrase alone also signs in, with no other device around.

Email and password are optional, in the account settings: with them you can sign in by typing on any device and confirm deletion with the password. One password for the account and the encryption; it never leaves the device.

Day to day. Sync runs by itself. Conflicting edits are merged or kept as conflict copies; deleted files and older versions are in the file history and the trash, as in selfsync. The settings show your storage use, the account’s sign-ins and devices (any of them can be revoked) and the plans. You can sign out or delete the account with all its data there too.

Disclosures

• Account required. It is created with one press inside the plugin, without an email or a password; you can add them later. Pressing Start accepts the terms of service.
• Paid plans. There is a free plan; larger plans will be paid. Plans that are not available yet are shown greyed out.
• Network use. The plugin talks only to the Selfsync Cloud servers in the region you pick when creating the account: CIS or Europe. Notes, file names and folder names are encrypted on your device before they leave it; the service cannot read them.
• No telemetry. The plugin collects no analytics. The server keeps what sync needs (device and sign-in names, the email if you added one, encrypted data sizes and times).
• What stays on the device. The account key and, until you mark it as written down, the recovery phrase words live in this device’s Obsidian local storage (not in the vault folder). The connect QR code carries the account key: show it only to your own device.
• Files outside the vault API. On desktop the sync engine uses Node's fs module, only inside your vault folder and the plugin's own folder: to replace files atomically (so a crash never leaves a half-written note) and to read large files in parts. On mobile it uses the Obsidian vault API only.
• Clipboard. The plugin writes to the clipboard only when you press a copy button (recovery phrase, connect code, sync log). It never reads the clipboard.
• Losing every device without a written-down phrase means lost data. The service holds no key to your notes, so support cannot restore access. Notes on your devices stay.

Source and audit

This repository adds only the cloud screens: account creation and sign-in, the recovery phrase, plans and device connection. The sync engine is the open selfsync project at a released tag, kept in core/: its plugin sources and styles, its MIT license and the engine compiled to WebAssembly. core/SOURCE names the tag and commit. CI rebuilds core/ from that tag with scripts/core.sh check and fails unless the result is byte-identical, so core/ cannot drift from the published selfsync.

Building the plugin needs only Node:

git clone https://github.com/Darkildo/selfsync-cloud
cd selfsync-cloud
npm ci && npm run build      # main.js, styles.css
npm test

To check core/ yourself (needs Rust, wasm-bindgen-cli and wasm-opt of the versions the script names):

scripts/core.sh check

Release files are built in GitHub Actions and carry a provenance attestation: gh attestation verify main.js -R Darkildo/selfsync-cloud.

The end-to-end test runs against the Selfsync Cloud server when SELFSYNC_CLOUD_BIN points to its binary; without it, the test is skipped. It checks that no request body ever carries a note or a file name in clear text.

License

PolyForm Shield 1.0.0: you may read, run, change and share this code for any purpose except building a product that competes with Selfsync Cloud. core/ is selfsync under the MIT license.