// Self-hosted sync infrastructure

Your team and your AI agents work from one shared brain.

Raven Sync keeps your company knowledge base in sync as plain files on every machine. Concurrent edits merge automatically, each member sees only the folders you grant, and every file stays on disk.

automatic merge · per-folder access control · files stay on disk

Sync your vault See how it works

My whole company runs from our markdown vault. But how do I share it with my team?

the CEO's machine: company-kb/

company-kb/
├ strategy/     plans · decisions · processes
├ marketing/
├ engineering/
├ clients/      one folder per client
├ people/
└ harness/      claude · codex: the agents work here too

sarah needs marketing/, mike needs engineering/, but I need to see everything.

Raven Sync is the solution I was looking for.

admin machine: one conversation

● you
  set up our company vault. marketing and engineering each get
  their folder to edit, strategy/ is read-only for both.
  then add sarah and mike.

● assistant
  ✳ loading skill: ravensync
  $ ravensync vault create acme
  $ ravensync team create acme marketing
  $ ravensync grant add --actor ceo acme marketing marketing/ write
  $ ravensync grant add --actor ceo acme marketing strategy/ read
  … engineering set up the same; sarah and mike added, tokens issued
  ✓ vault ready: 2 teams, 2 members, per-folder rights in place

  Send sarah and mike their enroll commands. One paste on their
  machine and their folders appear on disk, synced at every login.

Claude Code, Codex, or any agent works: it is a real CLI. Members join with one command that authenticates first and only then writes to disk; a wrong token fails immediately and leaves nothing behind.

// How it works

Work with synced local files.

The fastest way for humans and AI agents to work together.

The admin sets up the vault

Create the vault, teams, and per-folder grants on one server: a single Go binary over SQLite. No cluster, no external services.

A member runs one command

enroll writes the config and token, registers login autostart, and runs the first sync. The same command on macOS, Linux, and Windows.

Files flow to disk

Each member receives only what they are granted, filtered at distribution. Concurrent edits merge automatically. It is not a web app: it is your disk.

// What it does

Infrastructure, not a knowledge app.

Automatic 3-way merge

Concurrent edits to the same markdown, YAML, or JSON merge key-by-key; code and text get a line-level merge; binaries fall back to server-ordered last-writer-wins. Both edits survive.

No conflicted-copy files

A genuine overlap never produces a file (conflict copy).md sibling. It flags the file for review and keeps every version in history.

Per-folder access control

Team-based grants enforced server-side on every read path: pull, version history, and the conflicts listing. A revoked grant cuts off old versions too, not just future pulls.

Files on disk, agent-native

Every editor and every AI agent works with the files natively. No editor, no UI, no semantic layer to work around.

One-command onboarding

enroll handles config, token, login autostart, and first sync on macOS, Linux, and Windows. The daemon restarts on crash and starts at every login.

Nothing rewritten in your files

No injected IDs, markers, or metadata. All bookkeeping lives out-of-band. A file the engine never merged is byte-identical on every machine, so Obsidian and OKF vaults stay intact.

Self-hosted, one binary

Server, daemon, and CLI are one Go module over SQLite. Static binaries, no external database, no runtime dependencies. Run it on your own infrastructure.

No telemetry

The binaries never call home. No analytics, no cookies, no phone-home. Append-only history and a server-side git mirror keep an always-available exit.

// Why not X

Where the alternatives stop.

No product ships all three of concurrent-edit merge, per-folder access control, and local files on disk. Each alternative solves at most two.

Syncthing

Peer-to-peer sync of real files on disk, but no concurrent-edit merge and no per-folder team access control. Two edits to one file collide.

Dropbox / Google Drive

Cross-machine sync, but concurrent edits produce conflict copies, there are no per-folder team grants, and cloud placeholders are not agent-native. It is someone else's cloud.

Bare Git

Excellent history, but manual three-way merge and per-repo access only. Splitting repos to isolate departments breaks paths, and it is hostile to non-technical members.

Notion-class apps

Real merge and access control, but content is not files on disk. Agents cannot work natively, and exit is hard.

// Works with what you already use

Because it is just files.

Raven Sync adds no format and no lock-in. Whatever reads a folder of files already works.

Obsidian
Claude Code
Codex
VS Code
Any editor
Any AI agent

Any file type syncs. This is how each kind is handled when two people edit at once:

Markdown, YAML, JSON

First-class knowledge formats: concurrent edits merge key-by-key, YAML frontmatter included, and both edits survive. Untouched parts keep their exact formatting, including key order, quoting, and comments.

Code, scripts, any plain text

Line-level merge, the way git resolves parallel work. Prompts, configs, shell scripts, source files.

Images, PDFs, binaries

Sync unchanged. When two machines race, the newest version wins and every earlier version stays in history.

// Get started

Deploy it with us or on your servers.

Two ways to run Raven Sync. Deploy it on your own infrastructure with our guidance, or try a hosted instance first; we reply personally.

Hosted instance

A dedicated instance on EU infrastructure with backups and an audit log, so you get the product without running the server yourself. Free 14-day trial: we provision your instance and send you everything you need to connect, usually within one business day.

Self-hosted, with guidance

We deploy Raven Sync on your own infrastructure and help you design teams, grants, and member enrollment. Your data never leaves your perimeter.

Name

Company

People sharing the vault

Deployment

What are you looking to sync?