PKV Sync

by cyberkurry
5
4
3
2
1
Score: 52/100

Description

Release mirror for the PKV Sync Obsidian plugin - self-hosted, Git-backed vault sync. Source and issues: CyberKurry/pkv-sync

Reviews

No reviews yet.

Stats

1
stars
462
downloads
0
forks
161
days
5
days
5
days
0
total PRs
0
open PRs
0
closed PRs
0
merged PRs
2
total issues
0
open issues
2
closed issues
24
commits

Latest Version

5 days ago

Changelog

PKV Sync plugin 1.10.0. Changelog: https://github.com/CyberKurry/pkv-sync/blob/main/CHANGELOG.md#1100---2026-11-15

Plugin file checksums:

e0611c3f6ceecee374b4f1ea61b8935bea38f4fd43313824bfdfbb7bec893887  main.js
7847c8a640f674f964bc685991f96ed9c527de75db1d1350f8ffd605c8b496d7  manifest.json
f8568b282cf7bd4e5bf3328974e6a12a36a3e9211f440dc937e8c4ab84db80b8  styles.css

README file from

Github

PKV Sync

Self-hosted, Git-backed synchronization for Obsidian.

This repository is the release mirror for the PKV Sync Obsidian plugin: the plugin source tree and release artifacts, published automatically from the main repository on every release. Pull requests are not accepted here — development happens in the main repository. Issues are welcome here or in the main repository.

简体中文

Current release

PKV Sync 1.10.2 ships its MCP Registry metadata under the canonical GitHub namespace case (io.github.CyberKurry/pkv-sync). The product content matches 1.10.1: an edit made while a pull downloads a file becomes a visible conflict instead of overwriting the other device's committed version, a refused file is reported on every pass instead of showing a green status, one per-file rejection no longer wedges the vault, moving a note with a non-ASCII name keeps its Markdown links, and an interrupted self-update restores the previous build. Upgrade the server and plugin together.

What it is

PKV Sync keeps your vaults in sync across devices through a server you host. Git is the source of truth: every change is a commit, with per-file history, diff, restore, and vault-level rollback.

Highlights

  • Multi-user, multi-vault sync with sub-second propagation (SSE)
  • Full version history: per-file diff/restore and vault-level rollback
  • Three-way automatic merge for concurrent text edits; remaining conflicts surface as resolvable .conflict-* files with an in-app diff view
  • Git-native access: read-only git clone of your vault over HTTPS with any Git tooling
  • Built-in MCP server, so your own AI agent can read and maintain your notes
  • Admin web UI, Prometheus metrics, and a backup/restore/verify CLI
  • Available in English, 简体中文, 繁體中文, 日本語, and 한국어
  • One-command migration from Obsidian Sync

Requirements

This plugin requires a self-hosted PKV Sync server. You deploy and operate it yourself — there is no third-party service, and your notes never leave your own infrastructure.

Quick start

  1. Deploy the server (single binary or Docker Compose — see the admin manual), then open https://your-host/setup to create the first admin account.
  2. Install PKV Sync from the Obsidian community plugin directory and enable it.
  3. In the plugin settings, enter your server URL and deployment key, sign in, and pick or create a vault. Sync runs automatically; a manual sync command is also available.

Privacy

The plugin communicates only with the server URL you configure. There is no telemetry and no analytics. The server administrator (you) can read vault content stored on the server; see the security policy and the deployment hardening guide for details.

Documentation and support

License

AGPL-3.0