Loading Settler...
Loading Settler...
Loading documentation...
Settler matches financial records across systems, surfaces every mismatch as a structured exception, and produces auditable proof for each run. This guide covers two paths: managed cloud and self-hosted open source.
Settler is a reconciliation engine and exception-management system. It matches records across two or more data sources (payment processors, banks, ERPs, CSVs), surfaces every mismatch as a structured exception, and produces hash-linked proof artifacts for each run.
Each reconciliation run produces: matched records (with tolerance metadata), exceptions (unmatched or conflicting records), a run summary with counts, and a proofpack — a replayable evidence artifact you can export, share, or use for audit review.
Every workspace in Settler is tenant-scoped. Runs, exceptions, evidence, API keys, and exports are isolated to your workspace. Super-admin access is separate and explicitly declared in the role system.
Sign up, connect your data sources, and run reconciliation without infrastructure to manage.
Sign up at settler.dev. After signup you will be prompted to create a workspace — this is your tenant scope for all runs, exceptions, and proof artifacts.
Create accountGo to Console → Integrations and add your first adapter (Stripe, a database, or a CSV upload). Settler will ingest and normalize records for matching.
Open onboardingOnce your data source is connected, trigger a run from the Console → Runs page or via the API. Settler will match records and surface every exception.
View runsOpen Console → Exceptions to see every unmatched or conflicting record. Each exception shows provenance, evidence, and suggested actions.
View exceptionsEach completed run produces a proofpack — a hash-linked evidence artifact you can export for audit, close packs, or compliance review.
Open proof explorerRun the Settler engine on your own infrastructure. Full Apache 2.0 OSS — no vendor dependency.
Clone the repository and install dependencies. Settler requires Node.js 20+, pnpm, and a PostgreSQL database.
git clone https://github.com/Hardonian/Settler && pnpm installCopy .env.example to .env and fill in your database URL and Supabase credentials. See SETUP.md for a full variable reference.
cp .env.example .envApply the Prisma schema to your database and start the development server.
pnpm prisma migrate deploy && pnpm devBefore connecting production data, read the architecture overview to understand tenant isolation, authz, and data flow.
Architecture overviewFirst value in 30 minutes — checkpoints included.
Full REST API documentation.
TypeScript/Node.js SDK.
Available data source adapters.
Roles, scopes, and API keys.
Real-time event notifications.
Cloud, managed ops, and enterprise tiers.