Documentation

Getting started

Install: one command on macOS, Linux, or Windows (WSL2), or Docker Compose for a shared team server. Every install is free forever on one repository, with a 7-day trial of the Gateway on it.

How it works: the full walkthrough: indexing, hybrid retrieval, grounded answers, and a dashboard session on video.

Using SourceVault

Settings and features: every dashboard setting explained. Full git history, the history backend, licensed features, plan limits, and the environment variables operators use instead.

Commands and integrations: the Hermes plugin's slash commands, the LLM-callable tools, and the MCP server that exposes the engine to any MCP client.

The Gateway

Gateway reference: writing an access policy (rule fields, globs, fail-safe behaviour), what the DLP pass redacts, how the audit chain is verified and exported, AI-change provenance, and minting and scoping named agent identities.

MCP server setup: connecting Claude Code or any MCP client in one line, running it under a named agent, what a cloud-backed client sends to its vendor, and the tools, resources, and prompts.

Govern Claude Code in ten minutes: install, turn the Gateway on, write a deny rule, give Claude Code a named identity, and read the console and the report, with every command and what it prints.

Sample activity report: the quarter-to-date report a Team install produces, rendered in full from a seeded install, with the Markdown to download.

Sample compliance evidence summary: the one page a SOC 2 or ISO 27001 reviewer files, six controls with what the records show and how to verify each, from the same seeded install, with the PDF to download.

Reference

Benchmark: how answer quality is measured, with the methodology and current numbers.

Air-gapped installs: offline bundles, local models, and the zero-egress verification procedure.

Changelog: what shipped, version by version.

Comparison: how SourceVault differs from cloud code assistants, and where each fits.