Getting Started

Stand up your own Sannvit Ledger instance, from a cold checkout to a working audit chain.

This section walks through standing up a Sannvit Ledger instance end to end — the append-only, hash-chained audit trail that seals every LLM call, tool invocation, and retrieval an agent makes into a per-org, independently re-verifiable chain.

What you're setting up

The stack has five moving pieces:

Service	What it does
Postgres	The only database — holds the ledger schema and Keycloak's own schema, no separate pooler or REST layer in front of it
Keycloak	Authentication for the dashboard and service-to-service tokens
Ledger API	Ingests agent activity, seals it into the per-org hash chain, and runs the alerting/integrity-check loop
Dashboard	The browser UI for review, alerting, and evidence export
Blob storage	Holds payload content — the ledger itself only stores a pointer + hash — bundled via RustFS, or point it at your own S3-compatible bucket

Where to start

Hosting with Docker — the fastest path to a running stack, on a single host, for dev or production.
Hosting on Kubernetes — a Helm chart for a client cluster that needs horizontal scaling beyond one Compose host.

More paths (native dev without containers) will land here as this section grows.

Overview

What the Sannvit Ledger is, how it's built, and where to go next.

Hosting with Docker

Run the full Sannvit Ledger stack — Postgres, Keycloak, the ledger API, blob storage, and the dashboard — with Docker Compose.