Obsidian, governed for your whole company
Obsidian is perfect for a single person. The moment a company relies on those notes, you need governance Obsidian was never built to give. Ledger keeps your vault Obsidian-native — portable Markdown with [[wikilinks]] and YAML frontmatter — and adds the enterprise layer on top. Connect a real vault for two-way sync, or load the new Obsidian plugin to get that layer right inside Obsidian. Keep editing in Obsidian, never get locked in.
Structured fields (type, owner, reviewed_on, hostname…) are standard frontmatter Obsidian reads natively — and Ledger governs.
Wikilinks resolve in both Ledger and Obsidian, so backlinks and the dependency graph work either way. Ledger adds a navigable links/graph view.
Point Ledger at a folder of .md for continuous two-way sync — folders, tags, frontmatter and links carry over both ways. Or export back out and re-open in Obsidian. No cage.
One company vault, with per-space scopes: who can read, edit, approve, or publish. Admin, Editor, Reviewer, Viewer, and read-only Portal roles — a concept a personal vault simply doesn't have.
Every page carries an owner and a last-reviewed date. Ledger flags stale docs, records who approved which version, and re-opens approval after an edit.
Share a space with non-editors and auditors as a self-contained read-only HTML — they read, they can't change anything, they need no account.
Instant search across every space; an append-only audit trail; and single sign-on across the suite (cloud tier / Keystone).
Not a one-time import — a continuing link. Point Ledger at your real Obsidian vault folder and it reconciles both directions at the granularity of individual .md files.
Change a note in Obsidian, change the same page in Ledger, hit ⇄ Sync now (or leave auto-sync on). Ledger keeps a per-file content snapshot from the last sync and uses it to decide what moved: only-one-side-changed copies across, new files create on the other side, and a delete only mirrors when the surviving side is unchanged.
When both sides changed the same file, the on-disk file (Obsidian, your editor of record) wins — and your prior Ledger version is preserved in version history, where you can diff and restore it. An edit always beats a delete. Nothing silently disappears.
Dot-folders like .obsidian, .git and .trash are skipped, so your config, plugins and themes are never touched. Only .md files sync. And because Ledger stores zero secrets, syncing the vault writes none.
Once you're signed in, the sync panel adds ☁ Push to org cloud — after reconciling Obsidian ↔ Ledger, push the merged result to your team's shared org vault. The chain is Obsidian ↔ Ledger ↔ org cloud.
Browser folder sync uses the File System Access API in Chromium-class desktop browsers (Chrome, Edge, Brave, Arc). On Firefox and Safari, use the lossless Import/Export round-trip instead. The desktop experience ships as the Obsidian plugin below.
The flagship way to deliver "Obsidian for your whole company": a plugin you load into Obsidian itself. Because Obsidian is already the Mac/Windows/Linux/mobile host, the enterprise layer comes to you — no separate desktop app.
Paste a DosanjhLabs access token, click Verify, and your status bar shows your org. Then Push your whole vault to the shared org cloud, or Pull it back. Pull is non-destructive — it updates changed notes and creates missing ones, and never deletes a local note.
Mark current note reviewed stamps reviewed_on into frontmatter — the same field the web app reads. Show governance report opens a modal ranking notes never-reviewed → stale → fresh, with owner and age; click a row to jump to the note.
Publish documentation evidence sends structural signals only — paths, titles, type, reviewed_on, counts — to the shared evidence graph for Sightline. Note bodies are never sent.
The plugin reads and writes the same kb-state store the Ledger web app uses, so the two interoperate — work in Obsidian, govern in the web app, or both.
How sign-in works, honestly: Obsidian can't run the web app's redirect-based sign-in cleanly, so the plugin authenticates with a pasted access token (the standard Obsidian-plugin pattern). The token is a long-lived bearer credential stored only in this vault's local plugin data — never in a note, never logged. Network goes through Obsidian's requestUrl, and the tenant is always derived server-side from your verified token.
Install today by copying the plugin folder into <your-vault>/.obsidian/plugins/ledger-enterprise/ and enabling it — it's not yet listed in Obsidian's Community Plugins directory. One platform dependency: Keystone must accept pasted personal access tokens as bearer on the existing endpoints. Full plugin guide →
# 1. connect your real Obsidian vault folder — Ledger syncs both ways,
# file by file (or import a bundle / self-host against your git remote).
# frontmatter + [[links]] + folders carry over
# 2. keep editing in Obsidian — edits flow back into Ledger on the next
# sync; both-changed conflicts keep Obsidian's file and stash the prior
# Ledger version in history. (Or run the Obsidian plugin and never leave.)
# 3. govern in Ledger — assign owners, mark reviewed, approve versions,
# set who-can-edit-which-space, search across the whole org
# 4. publish a space as a read-only portal for auditors / non-editorsA documentation governance aid. Two-way folder sync is conflict-aware at the file level today; per-line 3-way auto-merge and real-time file watching are on the roadmap.