Overview
What LedgerForge is, what it is not, and how the documentation is organised.
LedgerForge is an open-source double-entry ledger for applications that move money. Use it to record wallet transfers, billing activity, reservations and refunds through an HTTP API, a Go library or a local MCP server. These pages describe v1.0.0. The repository holds the complete guides, runnable examples and the changelog.
What runs where
ledgerforgeis one Go binary.startruns the API server,workersruns the background workers,migrate upapplies schema migrations andverifyandauditrun the read-only checks.ledgerforge versionprints the installed release.ledgerforge-mcpis a separate binary that exposes a deployment to MCP clients over stdio.- PostgreSQL stores the financial records. Redis backs the queues and background workers.
- Typesense search, Prometheus metrics and OpenTelemetry tracing are optional.
What it does not do
LedgerForge records money movement. It does not connect to banks or payment rails, convert currencies, or decide your accounting model; those stay with your application. You can run it on your own infrastructure, or have the LedgerForge team operate a dedicated deployment for you with LedgerForge Cloud.
Pages
- QuickstartRun LedgerForge locally with Docker and post a balanced transfer through the HTTP API.
- ConceptsLedgers, balances, precision, references, transaction states, holds, refunds and previews.
- API overviewAuthentication, the main endpoints, request and response shapes, and error handling.
- Agent safetyPer-key spending policies, shared budgets for delegated keys and independent approval holds.
- MCP serverRun ledgerforge-mcp locally, enable write tools deliberately and bind it to an API key.
- VerificationAccounting replay, the versioned hash chain, checkpoints and external anchoring.
- SecurityScoped keys, delegation, revocation, legacy keys, error handling and webhook signatures.
- DeploymentInstallation, configuration, secrets, TLS, rate limits, workers and webhook destinations.
- UpgradesSupported upgrade paths to v1.0.0, the integrity migrations and the checks to run afterwards.